A brine-works municipal payroll replica may lag behind the write region, but never by more than two minutes or five versions. Which Cosmos consistency level matches that requirement?
Select an answer to reveal the explanation.
Short Explanation
Lag is fine—unbounded lag is not. Bounded staleness is the “never more than K versions or T time” dial. That matches a two-minute / five-version payroll replica ceiling.
Full Explanation
Bounded staleness guarantees that reads lag the write region by at most K versions or T time interval—the two official staleness knobs. Eventual has no such bound. Session scopes consistency to a client session rather than a global K/T lag budget. Consistent prefix preserves order for transactional batches but does not define the K-or-T staleness window described here.