AZ-305 Practice Question 56: Cosmos Multi Region Writes
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 6 · question 6 of 10
A global booking application uses Azure Cosmos DB with East US as the only write region and West Europe as a read replica. Booking offices in both continents write all day. The business now requires that both offices keep accepting writes without interruption or manual failover if either region becomes unavailable.
What should you do?
Show answer and explanation
Answer:
With multi-region writes, every region of the account accepts both reads and writes. If one region goes down, the applications in the other keep writing to their local region without waiting for a failover. Because the same item can be updated in two regions at once, the design must include a conflict resolution policy, such as last writer wins or a custom procedure.
Option A improves recovery but not continuity. With a single write region, service-managed failover promotes another region after an outage is detected, so writes stop until the promotion completes. The requirement says writes must not be interrupted.
Option C is a restore, not a failover. Point-in-time restore creates a new account, which takes time, needs manual steps, and misses the required continuity.
Option D does not add write availability. Consistency levels control read guarantees, and strong consistency is not available for accounts configured with multiple write regions.
Reference: Distribute your data globally with Azure Cosmos DB