Home › Azure AZ-204 › cloudcomputing › az204storage › What is the trade-off when using Cosmos DB sessi…
What is the trade-off when using Cosmos DB session consistency (the default)?
AWrites never succeed
BReads return random values
CThe client sees its own writes (read-your-writes) but other clients may see slightly older data — best balance of latency and consistency for most apps
DAll clients always see the same value at the same time globally
Answer & Solution
Correct answer: C. The client sees its own writes (read-your-writes) but other clients may see slightly older data — best balance of latency and consistency for most apps
Session consistency is the most-used default: a single session sees consistent reads (read-your-writes); cross-session staleness is bounded. The other options misstate it.
Related questions
An app must encrypt user-uploaded blobs using a key the customer controls, rotates, and auCosmos DB's Change Feed emits document changes in order. Which scenario is its CANONICAL uWhich Azure storage feature lets you fire an Azure Function when a new blob is uploaded?Which Cosmos DB feature lets a single container handle a sudden 10x traffic burst WITHOUT Which Azure storage feature continuously replicates blobs to a paired region for region-diWhich Azure storage feature lets you grant a client temporary download access to a specifiWhich Cosmos DB concept determines the physical sharding strategy — how documents are distWhat is Cosmos DB's consistency model that guarantees clients see writes in the same globa