DP-900 Practice Question: Describe considerations for working with non-relational data on Azure
This DP-900 practice question tests your understanding of describe considerations for working with non-relational data on azure. 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. A key principle to apply: eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB.. 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 social media app uses Azure Cosmos DB (NoSQL API) to store user profile data. The app is read-heavy and must serve content with the lowest possible latency to users worldwide. The data is updated by users, and the business has determined that eventual consistency is acceptable because immediate consistency after a write is not critical for profile views. Which consistency level should they choose to minimize read latency?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "minimum / minimize"
Why it matters: Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Eventual
Eventual consistency is the correct choice because it offers the lowest read latency by allowing reads to return data immediately without waiting for replication to complete. Since the app is read-heavy, global, and can tolerate eventual consistency for profile views, this consistency level minimizes the time to serve content by not imposing any ordering or staleness guarantees on replicas.
Key principle: Eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Eventual
Why this is correct
Eventual consistency provides the best read performance and availability, with no ordering guarantees.
Clue confirmation
The clue word "minimum / minimize" in the question point toward this answer.
Related concept
Eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB.
✗
Strong
Why it's wrong here
Strong consistency guarantees linearizability but increases read latency because it must contact replica quorums.
✗
Bounded staleness
Why it's wrong here
Bounded staleness allows a configurable staleness window but still imposes some latency compared to eventual.
✗
Session
Why it's wrong here
Session consistency guarantees monotonic reads for a single session, but read latency is higher than eventual.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often choose Session consistency because it is the default for many Azure Cosmos DB SDKs, but the question explicitly asks for the lowest read latency with eventual consistency acceptable, making Eventual the correct answer despite Session being a common default.
Detailed technical explanation
How to think about this question
Under the hood, Azure Cosmos DB's eventual consistency uses a quorum-free read path where the client reads from the nearest replica without waiting for replication acknowledgments, leveraging a multi-master replication model with asynchronous propagation. In a real-world scenario, a user in Tokyo updating their profile might see the change immediately on their own device via session consistency, but a user in Brazil reading that profile would see the old data until the write propagates, which is acceptable here. The trade-off is that eventual consistency provides the lowest read latency at the cost of potential read-your-writes inconsistency across regions.
KKey Concepts to Remember
Eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB.
It provides no ordering guarantees for reads; data may be stale.
Writes are asynchronously replicated across all regions.
Ideal for scenarios where immediate consistency after a write is not critical.
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
Eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB.
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. Eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB. 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-900 question in full detail.
Review eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB., then practise related DP-900 questions on the same topic to reinforce the concept.
Describe considerations for working with non-relational data on Azure — This question tests Describe considerations for working with non-relational data on Azure — Eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB..
What is the correct answer to this question?
The correct answer is: Eventual — Eventual consistency is the correct choice because it offers the lowest read latency by allowing reads to return data immediately without waiting for replication to complete. Since the app is read-heavy, global, and can tolerate eventual consistency for profile views, this consistency level minimizes the time to serve content by not imposing any ordering or staleness guarantees on replicas.
What should I do if I get this DP-900 question wrong?
Review eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB., then practise related DP-900 questions on the same topic to reinforce the concept.
Are there clue words in this question I should notice?
Yes — watch for: "minimum / minimize". Asks for the least resource use — fewest addresses, smallest subnet, lowest overhead. Eliminate over-provisioned options even if they would technically work.
What is the key concept behind this question?
Eventual consistency offers the highest availability and lowest read latency in Azure Cosmos DB.
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-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.
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.