DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DBDemo

By Microsoft · Question Mode

QuestionQ192

Optimize an Azure Cosmos DB solution

You have an Azure subscription containing an Azure Cosmos DB for NoSQL account named account1. The account uses strong consistency and is deployed in the East US, West US, and Central US Azure regions.

The round-trip time (RTT) between these regions is shown in the following table.

Question Image

What write latency should you estimate for write requests to account1?

  • A 150 ms
  • B 232 ms
  • C 282 ms
  • D 572 ms
Explanation

For an Azure Cosmos DB account that uses strong consistency across multiple regions, write latency is estimated as twice the RTT between the two farthest regions, plus 10 ms at the 99th percentile. East US and West US are farthest apart at 136 ms, so the estimate is 2 × 136 ms + 10 ms = 282 ms.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!