The correct choice is the SQL API with Session consistency because it supports multi-region writes with automatic conflict resolution using last-writer-wins (LWW) and guarantees a 99th percentile latency. Session consistency is the ideal balance for globally distributed applications, providing read-your-writes guarantees while keeping cross-region latency low, which is critical for the e-commerce scenario. On the AZ-305 exam, this question tests your understanding of how Cosmos DB multi-region writes conflict resolution consistency works—specifically that the SQL API is the only API offering LWW conflict resolution out of the box, and that Session consistency is the default and most widely used level for multi-region deployments. A common trap is choosing Eventual consistency for lower latency, but that sacrifices the read-your-writes guarantee needed for product catalog updates. Remember the memory tip: “SQL for LWW, Session for sync”—the SQL API handles conflicts automatically, and Session consistency keeps your own writes visible across regions.
AZ-305 Design data storage solutions Practice Question
This AZ-305 practice question tests your understanding of design data storage solutions. 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.
A global e-commerce company stores product catalog data in a JSON document format. The application requires low-latency reads and writes from multiple geographic regions. The solution must support multi-region writes with automatic conflict resolution and provide a guaranteed 99th percentile latency. Which Azure Cosmos DB API and consistency level should they choose?
The SQL API supports JSON documents, and Session consistency provides low latency with read-your-writes guarantee, suitable for e-commerce applications.
B
Table API with Eventual consistency
Why wrong: Table API is for key-value data, not JSON documents, and eventual consistency does not guarantee read-your-writes.
C
SQL API with Strong consistency
Why wrong: Strong consistency has higher latency and cannot guarantee 99th percentile latency across multi-region writes.
D
MongoDB API with Bounded staleness consistency
Why wrong: MongoDB API is also for document data, but Bounded staleness may still have higher latency than session, and session is more typical for e-commerce.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
SQL API with Session consistency
The SQL API with Session consistency is correct because it supports multi-region writes with automatic conflict resolution using last-writer-wins (LWW) and provides a guaranteed 99th percentile latency. Session consistency is the most widely used level for globally distributed applications, offering read-your-writes guarantees while maintaining low latency across regions.
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.
✓
SQL API with Session consistency
Why this is correct
The SQL API supports JSON documents, and Session consistency provides low latency with read-your-writes guarantee, suitable for e-commerce applications.
Related concept
Read the scenario before looking for a memorised answer.
✗
Table API with Eventual consistency
Why it's wrong here
Table API is for key-value data, not JSON documents, and eventual consistency does not guarantee read-your-writes.
✗
SQL API with Strong consistency
Why it's wrong here
Strong consistency has higher latency and cannot guarantee 99th percentile latency across multi-region writes.
✗
MongoDB API with Bounded staleness consistency
Why it's wrong here
MongoDB API is also for document data, but Bounded staleness may still have higher latency than session, and session is more typical for e-commerce.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume Strong consistency is required for low-latency multi-region writes, but Strong consistency is incompatible with multi-region writes and would actually increase latency, while Session consistency provides the right balance of performance and guarantees.
Detailed technical explanation
How to think about this question
Under the hood, Cosmos DB's multi-region writes use a conflict resolution policy, defaulting to last-writer-wins (LWW) based on a timestamp or custom property. Session consistency leverages a session token that is scoped to a client session, ensuring monotonic reads and writes without the overhead of Strong consistency, which requires quorum acknowledgments across all regions. In a real-world scenario, a global e-commerce catalog benefits from Session consistency because it allows users to immediately see their own updates (e.g., price changes) while other users may see slightly stale data, which is acceptable for product catalog reads.
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 AZ-305 question in full detail.
Design data storage solutions — This question tests Design data storage solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: SQL API with Session consistency — The SQL API with Session consistency is correct because it supports multi-region writes with automatic conflict resolution using last-writer-wins (LWW) and provides a guaranteed 99th percentile latency. Session consistency is the most widely used level for globally distributed applications, offering read-your-writes guarantees while maintaining low latency across regions.
What should I do if I get this AZ-305 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 →
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 company stores JSON documents for a mobile app backend. The data needs to be accessible from multiple global regions with low latency writes from any region. The app uses a client-side library that supports automatic conflict resolution for concurrent updates. Which Azure data service should they choose?
medium
✓ A.Azure Cosmos DB
B.Azure SQL Database
C.Azure Database for PostgreSQL
D.Azure Table Storage
Why A: Azure Cosmos DB is correct because it provides multi-region writes with automatic conflict resolution, which directly matches the requirement for low-latency writes from any global region. Its multi-master replication model allows any region to accept writes, and the client-side library can use last-writer-wins (LWW) or custom conflict resolution policies to handle concurrent updates seamlessly.
Last reviewed: Jun 11, 2026
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.
This AZ-305 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 AZ-305 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.