Describe considerations for working with non-relational data on Azure →hardMultiple ChoiceObjective-mapped
Strong Consistency for Global Reads with Low Write Latency in Cosmos DB
A global e-commerce company uses Azure Cosmos DB with multiple write regions to handle high traffic from users worldwide. For their order processing system, they must guarantee that once an order is recorded, all subsequent reads from any region see the most up-to-date order status. However, they also need low write latency globally. Which configuration should they choose to meet these requirements?
Quick Answer
The answer is to use single-region writes with strong consistency. This configuration guarantees that once an order is recorded, all subsequent reads from any global region see the most up-to-date status because Azure Cosmos DB synchronously replicates each write to all configured regions before acknowledging the commit, ensuring linearizability. For the DP-900 exam, this scenario tests your understanding of the trade-off between consistency models and write latency: strong consistency with single-region writes delivers low write latency within the primary region while still providing strong consistency for global reads, avoiding the conflict-resolution overhead of multi-region writes. A common trap is assuming multi-region writes are needed for low latency everywhere, but that sacrifices strong consistency. Remember the memory tip: “One writer, strong reader” — single-region writes keep writes fast and reads globally consistent.
⚠ Common exam trap
A common mix-up: candidates assume multi-region writes are needed for global low-latency writes, but they overlook that strong consistency cannot be combined with multi-region writes, and that single-region writes with strong consistency still provide low write latency in the primary region while guaranteeing immediate read freshness across all regions.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use single-region writes with strong consistency
Strong consistency with single-region writes ensures that all reads in any region return the most recent write, because Cosmos DB replicates writes synchronously to all regions when strong consistency is configured. This guarantees linearizability: once an order is committed, every subsequent read sees that update. Single-region writes avoid the conflict-resolution overhead of multi-region writes while still providing low write latency within the primary region, and reads from secondary regions are served from locally replicated data that is kept fully consistent.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use multi-region writes with strong consistency
Why it's wrong here
Incorrect. Strong consistency is not supported when multiple write regions are enabled. Multi-region writes only support eventual consistency.
When this WOULD be correct
If the question required maximum availability and low write latency globally, but did not require strong consistency for reads, then multi-region writes with eventual consistency would be correct. However, strong consistency is never available with multi-region writes.
- ✓
Use single-region writes with strong consistency
Why this is correct
Correct. Strong consistency provides immediate global consistency, but it requires a single write region. This trade-off meets the guarantee at the cost of slightly higher write latency for remote users.
- ✗
Use multi-region writes with bounded staleness consistency
Why it's wrong here
Incorrect. Bounded staleness is not available with multi-region writes. Only eventual consistency is supported in that configuration.
When this WOULD be correct
A scenario where the application can tolerate a bounded lag (e.g., up to 5 seconds) for reads, but requires low write latency globally and stronger guarantees than eventual consistency. For example, a social media feed where posts must be visible within a few seconds across regions, but not instantly.
- ✗
Use single-region writes with eventual consistency and implement application-level conflict resolution
Why it's wrong here
Incorrect. Eventual consistency cannot guarantee that all reads see the latest write immediately, which violates the requirement for strong global consistency.
When this WOULD be correct
In a scenario where the application can tolerate temporary inconsistencies (e.g., a social media feed) and requires low write latency globally with multi-region writes, but the application handles conflict resolution (e.g., last-writer-wins) to manage conflicts.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The DP-900 exam frequently reuses these exact scenarios with slightly different constraints.
✓Use single-region writes with strong consistencyCorrect answer▾
Why this is correct
Correct. Strong consistency provides immediate global consistency, but it requires a single write region. This trade-off meets the guarantee at the cost of slightly higher write latency for remote users.
✗Use multi-region writes with strong consistencyWrong answer — click to see why▾
Why this is wrong here
Strong consistency with multi-region writes is not supported in Azure Cosmos DB; multi-region write accounts can only use eventual or bounded staleness consistency. Thus, this option is technically impossible.
★ When this WOULD be the correct answer
If the question required maximum availability and low write latency globally, but did not require strong consistency for reads, then multi-region writes with eventual consistency would be correct. However, strong consistency is never available with multi-region writes.
Why candidates choose this
Candidates may assume that combining multi-region writes with strong consistency would provide both low write latency and strong consistency, not realizing that Azure Cosmos DB does not support this combination.
✗Use multi-region writes with bounded staleness consistencyWrong answer — click to see why▾
Why this is wrong here
Multi-region writes with bounded staleness consistency cannot guarantee that all subsequent reads from any region see the most up-to-date order status, because bounded staleness allows a lag (e.g., up to K versions or T time), so a read in a different region might see stale data before the write propagates.
★ When this WOULD be the correct answer
A scenario where the application can tolerate a bounded lag (e.g., up to 5 seconds) for reads, but requires low write latency globally and stronger guarantees than eventual consistency. For example, a social media feed where posts must be visible within a few seconds across regions, but not instantly.
Why candidates choose this
Candidates may think that combining multi-region writes (for low write latency) with bounded staleness (for some consistency) provides a good trade-off, but they overlook that the requirement for 'all subsequent reads from any region see the most up-to-date order status' demands strong consistency, not a bounded lag.
✗Use single-region writes with eventual consistency and implement application-level conflict resolutionWrong answer — click to see why▾
Why this is wrong here
Eventual consistency does not guarantee that all subsequent reads see the most up-to-date order status, which violates the requirement for immediate global consistency after writes.
★ When this WOULD be the correct answer
In a scenario where the application can tolerate temporary inconsistencies (e.g., a social media feed) and requires low write latency globally with multi-region writes, but the application handles conflict resolution (e.g., last-writer-wins) to manage conflicts.
Why candidates choose this
Candidates may think that eventual consistency with application-level conflict resolution can achieve both low latency and eventual correctness, overlooking the strict requirement for immediate consistency after writes.
Analysis generated from the official DP-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
Learn chapter
Data Roles and Core Concepts
Key term
Data
Data is raw, unprocessed information, like numbers, words, or measurements, that can be stored, processed, and analyzed by computers.
Key term
Azure Cosmos DB
Azure Cosmos DB is a fully managed, globally distributed NoSQL database service that offers fast reads and writes anywhere in the world with automatic scaling and multiple consistency models.
About these practice questions
One of 820 original DP-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
2 more ways this is tested on DP-900
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A global e-commerce platform uses Azure Cosmos DB to store product inventory data. Customers add items to their cart, which reduces the available inventory count. The application requires that after a customer adds an item, any subsequent read of that product's inventory from any region in the world must reflect the reduced count immediately. Which Cosmos DB consistency level should be used?
medium- A.Eventual consistency
- B.Consistent prefix consistency
- C.Session consistency
- ✓ D.Strong consistency
Why D: Strong consistency ensures that any read operation returns the most recent write, regardless of the region. Since the application requires that after a customer adds an item, any subsequent read of that product's inventory from any region must reflect the reduced count immediately, Strong consistency is the only level that guarantees linearizability and zero staleness across all replicas.
Variation 2. A global gaming company uses Azure Cosmos DB to store player scores and profiles. The application reads and writes player data from multiple regions worldwide. The company wants to ensure that when a player updates their high score in one region, any subsequent read from another region will always see the latest value, even if there is network latency between regions. Which consistency level should they choose?
medium- A.Strong
- B.Bounded staleness
- C.Session
- ✓ D.Eventual
Why D: When multi-region writes are enabled in Azure Cosmos DB, the only supported consistency level is eventual consistency. However, eventual consistency does not guarantee that reads always return the latest value—replicas may lag. Therefore, none of the given consistency levels can satisfy the requirement of always seeing the latest value across regions after a write in one region. The company would need to reconsider their architecture, such as using a single write region with strong consistency. Thus, no option is correct.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-900 exam.