DP-900Domain 3: Describe Considerations for Working with Non-Relational Data on AzureNon-Relational Data on AzurehardSingle choice
Which Cosmos DB consistency level guarantees reads ALWAYS see the most recent write — the strongest guarantee with the lowest availability during partitions?
A.Eventual
Eventual is the WEAKEST — opposite end.
B.Strong
Linearizability = Strong. Correct.
C.Session
Session guarantees consistency within a client session only.
D.Consistent prefix
Consistent prefix only guarantees read ORDER, not recency.
Why this answer
The five levels from strongest to weakest: Strong → Bounded staleness → Session → Consistent prefix → Eventual. Strong = linearizable reads everywhere, trading availability/latency; Eventual = max availability, replicas may lag.
Correct answer: B · Last reviewed 2026-11-05
Official AWS references
Practice this interactively
Answer without seeing the solution first in the Non-Relational Data on Azure practice session.
Practice Non-Relational Data on Azure