Describe considerations for working with non-relational data on Azure →mediumMultiple ChoiceObjective-mapped
Cosmos DB Consistency Level for Low Latency Read-Heavy Apps
A global social media app uses Azure Cosmos DB (NoSQL API) to store user profile data. The app is read-heavy and requires the fastest possible read performance worldwide. The data is updated by users and eventual consistency is acceptable because immediate consistency is not critical for profile views. Which consistency level should they choose to minimize read latency?
Quick Answer
The answer is Eventual consistency. This is the correct choice because Eventual consistency allows Azure Cosmos DB to serve reads from any replica without waiting for synchronization, making it the fastest option for a read-heavy app where immediate consistency is not required. Since the app prioritizes low latency for global profile views and accepts eventual consistency, this level eliminates any staleness bounds or write acknowledgments that would slow down read performance. On the DP-900 exam, this scenario tests your understanding of the trade-off between consistency and latency: Eventual offers the lowest read latency, while Strong offers the highest. A common trap is choosing Consistent Prefix or Session, which still impose some ordering or session guarantees that add overhead. Memory tip: think “Eventual = eventual updates, immediate reads” — the fastest path for read-heavy apps where perfect freshness isn’t needed.
⚠ Common exam trap
It's easy for candidates to assume Strong or Bounded staleness are required for any data that is updated, but the question explicitly states eventual consistency is acceptable, making Eventual the optimal choice for minimizing read latency.
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
✓
Eventual
Eventual consistency offers the lowest read latency because it allows reads from any replica without waiting for confirmation that the data is the most recent version. Since the app is read-heavy and eventual consistency is acceptable, this consistency level minimizes latency by not requiring any synchronization or staleness bounds.
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
Why it's wrong here
Strong consistency guarantees that reads always return the most recent write, but it requires writes to be acknowledged by all replicas, increasing latency for both writes and reads, which is not optimal for minimizing read latency.
- ✗
Bounded staleness
Why it's wrong here
Bounded staleness ensures reads are within a fixed time lag from the latest write. While it offers stricter guarantees than eventual, it still imposes some synchronization overhead, resulting in higher read latency than eventual consistency.
- ✗
Session
Why it's wrong here
Session consistency guarantees monotonic reads and writes within a single client session. Although it is efficient, it still requires some coordination, leading to slightly higher latency than eventual consistency.
- ✓
Eventual
Why this is correct
Eventual consistency provides the weakest guarantee but the lowest read latency. Reads are served from any replica without waiting for write propagation, making it ideal for read-heavy workloads where immediate consistency is not required.
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
Courseiva writes every DP-900 question from scratch — 820 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way 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 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?
medium- ✓ A.Eventual
- B.Strong
- C.Bounded staleness
- D.Session
Why A: 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.
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.