Microsoft Azure Developer Associate AZ-204 Practice Question

Bounded staleness guarantees that any read is within a user-defined interval measured in versions or time (for example, five minutes) while still allowing reads from local replicas in every region. This satisfies the requirement for predictable data freshness with global low-latency access. Strong consistency always returns the most recent committed write but increases write latency and can reduce availability in a multi-region setup because each write must be committed to all regions synchronously. Session consistency provides read-your-writes for a given client session but does not bound staleness for other sessions, so another user could receive data older than five minutes. Consistent prefix only guarantees that reads never observe out-of-order writes; they can be arbitrarily stale and therefore cannot enforce the five-minute freshness limit.