The answer is that Eventual consistency is the default consistency level for all new Azure Cosmos DB accounts, and Strong consistency is available in all Azure regions when the account is configured to use it, though it cannot be combined with multi-region writes. Eventual consistency is the default because it offers the highest throughput and lowest latency, making it the most cost-effective and scalable starting point for most workloads. Strong consistency guarantees linearizability, ensuring every read returns the most recent write, but this requires a single write region and incurs higher latency and reduced availability during regional outages. On the AZ-204 exam, this topic tests your understanding of the trade-offs between data consistency and performance, often appearing in scenario-based questions where you must choose the right level for a distributed application. A common trap is assuming Strong consistency works seamlessly with multi-region writes, but it only supports a single write region. Memory tip: think of Strong as “single-wire” — it locks writes to one region for guaranteed order.
AZ-204 Develop for Azure storage Practice Question
This AZ-204 practice question tests your understanding of develop for azure storage. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 of the following are correct about Azure Cosmos DB consistency levels?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Strong consistency is available in all Azure regions.
Option B is correct because Strong consistency is available in all Azure regions when the Cosmos DB account is configured to use it. However, it is important to note that Strong consistency cannot be combined with multi-region writes; it only supports a single write region. This ensures that all reads return the most recent write, but it comes at the cost of higher latency and reduced availability during regional outages.
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.
✗
Strong consistency provides the highest availability.
Why it's wrong here
Strong consistency provides the lowest availability.
✓
Strong consistency is available in all Azure regions.
Why this is correct
Strong consistency is supported globally.
Related concept
Read the scenario before looking for a memorised answer.
✗
Session consistency is the default consistency level for all new Cosmos DB accounts.
Why it's wrong here
Session is the default for .NET SDK, but not the account default.
✗
Bounded staleness consistency is the default consistency level.
Why it's wrong here
Bounded staleness is not the default.
✓
Eventual consistency is the default consistency level for all new Cosmos DB accounts.
Why this is correct
Eventual consistency is the default for new accounts.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Microsoft often tests the misconception that Strong consistency provides high availability, when in reality it sacrifices availability for consistency, and that Session consistency is not the default, leading candidates to incorrectly select Bounded staleness or Eventual consistency as defaults.
Detailed technical explanation
How to think about this question
Under the hood, Cosmos DB implements consistency levels using a quorum-based replication protocol. Strong consistency requires a majority quorum (R + W > N) for both reads and writes, ensuring linearizability. In contrast, Session consistency uses client session tokens to provide monotonic reads and writes within a single client session, which is the default because it balances performance and consistency for most applications. The trade-off is that Strong consistency can lead to write unavailability if a majority of replicas are unreachable, whereas Session consistency can tolerate more failures.
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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Develop for Azure storage — This question tests Develop for Azure storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Strong consistency is available in all Azure regions. — Option B is correct because Strong consistency is available in all Azure regions when the Cosmos DB account is configured to use it. However, it is important to note that Strong consistency cannot be combined with multi-region writes; it only supports a single write region. This ensures that all reads return the most recent write, but it comes at the cost of higher latency and reduced availability during regional outages.
What should I do if I get this AZ-204 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 AZ-204 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-204 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.