Users must always see their own changes immediately, but it's fine if other users see them a moment later. Which Azure Cosmos DB consistency level meets this at the lowest cost?
- A Strong
- B Bounded staleness
- C Session (correct answer)
- D Eventual
Shortcut: Read your own writes = Session consistency (the default). Strong and Bounded staleness add latency and RU cost this scenario doesn't need, and Eventual doesn't guarantee users see their own writes.
Session consistency guarantees read-your-own-writes within a client session and is the default for new accounts. Strong and Bounded staleness add latency and RU cost this scenario doesn't need, and Eventual doesn't guarantee users see their own writes.