Microsoft Azure Developer Associate AZ-204 Practice Question

Session consistency guarantees that a client will always read its own writes and reads will honor monotonic reads and writes within the same session token. Because the guarantee is scoped to the caller's session, the database does not have to coordinate all replicas, so it incurs lower latency and RU charges than the globally enforced Strong and Bounded Staleness levels. Eventual and Consistent Prefix offer even lower latency but cannot guarantee that a client will immediately observe its own writes. Therefore, the microservice should set Session consistency for its requests.