Match each Azure Cosmos DB consistency level on the left with its corresponding behavior or guarantee on the right.
- StrongGuarantees that reads always return the most recent version of an item, requiring a synchronous write commit across all replica sets before returning success.
- SessionProvides read-your-writes and monotonic read guarantees for a specific client connection, which is the default consistency level for new databases.
- Bounded StalenessGuarantees that reads may lag behind writes by a user-defined threshold of either operations () or time interval ().
- EventualProvides no ordering guarantees for reads, but offers the maximum throughput and lowest latency as replicas converge asymptotically.
Answer
Strong consistency matches with synchronous write updates and most recent version reads; Session consistency matches with connection-scoped read-your-writes and is the default setting; Bounded Staleness matches with configuration of staleness thresholds ( or ); Eventual consistency matches with no ordering guarantees and lowest latency.
Strong consistency matches with synchronous write replication because it ensures reads always receive the most recent committed state. Session consistency matches with connection-scoped guarantees and is the default level. Bounded Staleness matches with defined thresholds ( or ) because it guarantees reads do not lag beyond those limits. Eventual consistency matches with no ordering guarantees and lowest latency because replication is fully asynchronous.
Step-by-Step Solution
Key Concept
Azure Cosmos DB Consistency Levels