The answer is to consider global distribution capabilities with multi-region writes and the choice of consistency models. Azure Cosmos DB is designed for globally distributed, low-latency transactions because it offers multiple well-defined consistency levels—from strong to eventual—allowing you to tune the trade-off between data freshness and write speed. For a workload requiring low-latency reads and writes worldwide, selecting a weaker consistency model like session or eventual avoids the synchronous replication overhead of strong consistency, dramatically reducing write latency across regions. On the DP-203 exam, this question tests your understanding of how Cosmos DB’s multi-region write support and tunable consistency directly address global transactional needs, while Azure SQL Database relies on a single primary region for writes, making it less suitable for true global low-latency writes. A common trap is assuming SQL Database’s geo-replication offers the same write performance—it does not, as it uses asynchronous replication for reads only. Memory tip: “Cosmos for global writes, SQL for single-region ACID.”
DP-203 Design and implement data storage Practice Question
This DP-203 practice question tests your understanding of design and implement data storage. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which TWO factors should you consider when choosing between Azure SQL Database and Azure Cosmos DB for a transactional workload that requires low-latency reads and writes globally?
Option C is correct because Azure Cosmos DB offers multiple well-defined consistency models (strong, bounded staleness, session, consistent prefix, and eventual) that allow you to tune the trade-off between consistency and latency for globally distributed workloads. For a transactional workload requiring low-latency reads and writes globally, choosing the appropriate consistency model (e.g., session or eventual) can significantly reduce write latency by avoiding the overhead of synchronous replication required for strong consistency. This flexibility is a key factor when designing for global distribution with multi-region writes.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
ACID transaction support across multiple documents.
Cosmos DB offers five consistency models; SQL Database offers snapshot isolation.
Related concept
Read the scenario before looking for a memorised answer.
✗
Ability to run stored procedures.
Why it's wrong here
Both support stored procedures.
✓
Global distribution capabilities with multi-region writes.
Why this is correct
Cosmos DB offers turnkey global distribution, while SQL Database requires active geo-replication.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume ACID transactions (Option A) or stored procedures (Option D) are unique to one service, when in fact both Azure SQL Database and Azure Cosmos DB support these features, making them irrelevant as distinguishing factors for global low-latency workloads.
Detailed technical explanation
How to think about this question
Azure Cosmos DB's consistency models are implemented using a quorum-based replication protocol and a timestamp-based ordering system (e.g., using logical clocks or hybrid logical clocks). For example, the 'session' consistency model guarantees monotonic reads and writes within a single client session by using a session token that is passed with each request, allowing reads to be served from any replica while still providing a consistent view. In a real-world scenario, an e-commerce platform with users worldwide might use 'eventual' consistency for product catalog reads to achieve sub-10 ms latency, while using 'strong' consistency only for order placement to ensure no duplicate charges.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Design and implement data storage — This question tests Design and implement data storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Consistency models (strong, bounded staleness, session, eventual, consistent prefix). — Option C is correct because Azure Cosmos DB offers multiple well-defined consistency models (strong, bounded staleness, session, consistent prefix, and eventual) that allow you to tune the trade-off between consistency and latency for globally distributed workloads. For a transactional workload requiring low-latency reads and writes globally, choosing the appropriate consistency model (e.g., session or eventual) can significantly reduce write latency by avoiding the overhead of synchronous replication required for strong consistency. This flexibility is a key factor when designing for global distribution with multi-region writes.
What should I do if I get this DP-203 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This DP-203 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-203 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.