Question 9
UnclassifiedA global app needs low-latency reads but can tolerate slightly stale data for product catalog browsing. Which design choice should be reviewed?
Correct answer: B
Explanation
Cosmos DB consistency levels control the tradeoff between latency and freshness, and the replication design affects how quickly reads can be served from nearby regions. For a catalog that can tolerate "slightly stale data," reviewing these settings fits the need for "low-latency reads" without requiring strict real-time consistency.
Why each option is right or wrong
A. Whether all users can be administrators.
B. The Cosmos DB consistency level and replication design.
Azure Cosmos DB exposes five consistency levels—Strong, Bounded Staleness, Session, Consistent Prefix, and Eventual—so the read-latency versus freshness tradeoff is controlled at the database layer, not in the app code. For a globally distributed catalog, the replication topology and the chosen consistency level determine whether reads can be served from the nearest region with only bounded or eventual lag, which is exactly the condition described when slightly stale data is acceptable.
C. Whether to disable indexing entirely.
D. The color of the Azure portal theme.