Home › Azure AZ-305 › cloudcomputing › az305datastorage › Which Cosmos DB consistency level should an arch…
Which Cosmos DB consistency level should an architect recommend for a globally-deployed app where each USER must read their own writes but other sessions tolerate slight lag?
AEventual only (no read-your-writes)
BStrong consistency only (highest latency, single-region writes)
CSession consistency (the Cosmos default — read-your-writes within a session, bounded cross-session staleness)
DNo consistency
Answer & Solution
Correct answer: C. Session consistency (the Cosmos default — read-your-writes within a session, bounded cross-session staleness)
Session is the canonical read-your-writes balance (per AZ-305 §2 NoSQL). The other options either over-pay on latency or break the read-your-writes requirement.
Related questions
Which Azure data-platform service should an architect recommend for streaming ingestion + Which Azure SQL Database feature should an architect recommend to recover from a regional Which Azure storage replication option should an architect recommend for data that must suWhich Azure storage capability should an architect recommend to provide a hierarchical-namWhich Azure service should an architect recommend to ingest, transform, and orchestrate ETWhich Azure service should an architect recommend for petabyte-scale columnar analytics + Which Azure SQL Database feature should an architect recommend to scale a transactional daWhich Cosmos DB feature should an architect recommend to handle a sudden burst from 100 to