Automatic Failover
← Back to DP-420 Terminology Reference
Category: Data Distribution & Consistency
Summary: Policy that automatically promotes a new write region during a regional outage.
Overview
Automatic failover is a policy you configure on a multi-region Azure Cosmos DB account so that, if the current write region becomes unavailable, Azure Cosmos DB automatically promotes another read region to become the new write region without manual intervention, based on a configured region priority order.
More Info & Links
DP-420 Style Practice Questions
Q1. What does enabling automatic failover accomplish for a multi-region Azure Cosmos DB account?
- A. Automatically promotes another region to become the write region if the current write region fails
- B. Automatically creates new regions on demand
- C. Automatically deletes old backups
- D. Automatically increases RU/s during failures
Q2. What determines which region becomes the new write region during an automatic failover?
- A. The configured region priority order
- B. A random selection
- C. Whichever region has the most storage
- D. The region with the lowest RU/s
Answer Key
Answers are listed at the very end so you can attempt the questions first.
- Q1 (Automatic Failover): A. Automatically promotes another region to become the write region if the current write region fails — Automatic failover promotes a new write region automatically during a regional outage, based on priority order.
- Q2 (Automatic Failover): A. The configured region priority order — The region priority order you configure determines the sequence in which regions are promoted during failover.
DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB — term detail page
