A Cosmos DB account with bounded staleness consistency is configured with 5 seconds staleness. What is guaranteed?
- A Reads always see the latest write
- B Reads may be at most 5 seconds (or K operations) behind the leader (correct answer)
- C Each session sees its own writes
- D There are no consistency guarantees
Shortcut: Bounded staleness guarantees reads are at most K versions or T time behind the most recent write. It's stronger than session or eventual, suitable for apps that can tolerate brief staleness.