A glacier-guide booking Cosmos account enables multiple write regions, and an operator still tries to set Strong consistency. What should the developer know about that pairing?
Select an answer to reveal the explanation.
Short Explanation
Strong plus many write regions is a locked door—Microsoft does not offer that combo. Pick a weaker consistency when the account writes in multiple regions. This is a configuration rule, not a conflict-resolver design essay.
Full Explanation
When a glacier-guide booking Cosmos account enables multiple write regions, Strong consistency is not a valid pairing. Official documentation blocks Strong consistency together with multi-region writes. The developer must choose a weaker consistency level (Bounded staleness, Session, Consistent prefix, or Eventual) if the account will accept writes in more than one region, or keep a single write region if Strong is mandatory for the booking labels.
Strong does not silently convert to Eventual and continue; treating the conflict as an automatic downgrade hides a configuration error. Last-Writer-Wins conflict resolution does not unlock Strong with multi-region writes—conflict policies address concurrent writes under weaker multi-master setups, not the Strong restriction. Requiring Strong whenever more than one write region is enabled is the opposite of the rule and would leave the account in an unsupported state.
Exam caveat: this is a hard configuration constraint, not a soft performance hint. Portal and API validation should reject or prevent the combination; do not design as if conflict resolvers paper over Strong plus multi-region writes.
Operational check: before enabling a second write region, read the account’s default consistency; if it is Strong, lower it first, apply the multi-region write change, then validate booking reads under the chosen weaker level from each write region.