Configuring Auto-Failover Groups for Regional Disaster Recovery in Azure SQL Database
A global e-commerce company uses Azure SQL Database for its product catalog. The database is hosted in the West US region. To ensure the catalog remains available if West US experiences an outage, the company wants to configure a secondary database in East US that can be used for reads and can be automatically promoted to primary during a disaster. They require a Recovery Point Objective (RPO) of less than 5 seconds and a Recovery Time Objective (RTO) of less than 30 minutes. Which feature should they implement?
Quick Answer
The answer is auto-failover groups. This feature is the correct choice because it enables automatic, orchestrated failover of an Azure SQL Database from a primary region, such as West US, to a secondary region like East US during an outage, while meeting a Recovery Point Objective of less than 5 seconds through active geo-replication and a Recovery Time Objective of under 30 minutes. The secondary database also supports read-only queries, and the failover group ensures the entire group of databases fails over as a unit, preserving the same connection string. On the Microsoft Azure Data Fundamentals DP-900 exam, this scenario tests your understanding of high-availability and disaster recovery options; a common trap is confusing failover groups with active geo-replication alone, but remember that failover groups add automatic failover and read-scale capabilities. Memory tip: think "group failover for zero-touch recovery" to distinguish it from manual geo-replication.
⚠ Common exam trap
Candidates often confuse active geo-replication with auto-failover groups, assuming both provide automatic failover, but only auto-failover groups offer the orchestrated, automatic promotion required for the specified RTO.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Auto-failover groups
Auto-failover groups (Option B) are the correct choice because they provide automatic, orchestrated failover of a primary Azure SQL Database to a secondary region (East US) during an outage, meeting the RPO of less than 5 seconds (typically 5–10 seconds for active geo-replication) and RTO of less than 30 minutes (usually under 1 hour). The secondary database can be used for read-only queries, and the failover group ensures the entire group of databases fails over as a unit, maintaining the same connection string.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Active geo-replication
Why it's wrong here
Active geo-replication creates readable secondaries, but failover is manual, not automatic, and does not provide an RTO of under 30 minutes in an automated manner.
When this WOULD be correct
Active geo-replication would be correct if the requirement was for a readable secondary database with manual failover, and the RTO could be longer (e.g., over 30 minutes) or the failover could be initiated manually by an operator.
- ✓
Auto-failover groups
Why this is correct
Auto-failover groups provide automatic failover to a secondary region, include a readable secondary, and meet the RPO of 5 seconds and RTO of 30 minutes.
- ✗
Geo-restore
Why it's wrong here
Geo-restore restores a database from a geo-replicated backup, but has a longer RTO (typically hours) and no automatic failover capability.
When this WOULD be correct
If the company only needed to recover the database after a regional outage with no requirement for a readable secondary or automatic failover, and could tolerate an RPO of 1 hour and an RTO of several hours, geo-restore would be the appropriate feature.
- ✗
Transactional replication
Why it's wrong here
Transactional replication is used to replicate data changes to other databases for distributed scenarios, not for automatic failover during a regional outage.
When this WOULD be correct
Transactional replication would be correct if the company needed to replicate specific tables or subsets of data to a secondary database for reporting or offline processing, with tolerance for higher latency and manual failover, and did not require automatic failover or strict RPO/RTO.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The DP-900 exam frequently reuses these exact scenarios with slightly different constraints.
✓Auto-failover groupsCorrect answer▾
Why this is correct
Auto-failover groups provide automatic failover to a secondary region, include a readable secondary, and meet the RPO of 5 seconds and RTO of 30 minutes.
✗Active geo-replicationWrong answer — click to see why▾
Why this is wrong here
Active geo-replication provides a readable secondary database with an RPO of less than 5 seconds, but it does not support automatic failover; manual failover is required, which cannot guarantee an RTO under 30 minutes.
★ When this WOULD be the correct answer
Active geo-replication would be correct if the requirement was for a readable secondary database with manual failover, and the RTO could be longer (e.g., over 30 minutes) or the failover could be initiated manually by an operator.
Why candidates choose this
Candidates may confuse active geo-replication with auto-failover groups because both involve geo-replication and readable secondaries, but they overlook that auto-failover groups are needed for automatic failover to meet strict RTO requirements.
✗Geo-restoreWrong answer — click to see why▾
Why this is wrong here
Geo-restore restores a database from a geo-replicated backup, but it does not provide a readable secondary or automatic failover; RTO can be hours, not under 30 minutes, and RPO is typically 1 hour, not under 5 seconds.
★ When this WOULD be the correct answer
If the company only needed to recover the database after a regional outage with no requirement for a readable secondary or automatic failover, and could tolerate an RPO of 1 hour and an RTO of several hours, geo-restore would be the appropriate feature.
Why candidates choose this
Candidates may confuse geo-restore with geo-replication because both involve geographic redundancy, and the term 'restore' might seem like a valid disaster recovery option without considering the strict RPO and RTO requirements.
✗Transactional replicationWrong answer — click to see why▾
Why this is wrong here
Transactional replication does not support automatic failover or RTO under 30 minutes; it requires manual intervention to promote a secondary and typically has higher latency, making it unsuitable for the sub-5-second RPO and sub-30-minute RTO requirements.
★ When this WOULD be the correct answer
Transactional replication would be correct if the company needed to replicate specific tables or subsets of data to a secondary database for reporting or offline processing, with tolerance for higher latency and manual failover, and did not require automatic failover or strict RPO/RTO.
Why candidates choose this
Candidates may confuse transactional replication with geo-replication because both involve copying data to another region, but they overlook the automatic failover and strict RPO/RTO requirements that only auto-failover groups provide.
Analysis generated from the official DP-900blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
Courseiva writes every DP-900 question from scratch — 820 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on DP-900
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is designing a relational database solution on Azure for an e-commerce platform. They need to ensure high availability and automatic failover in case of a regional outage. Which Azure service should they use?
easy- ✓ A.Azure SQL Database with active geo-replication
- B.Azure SQL Managed Instance with local redundancy
- C.Azure Database for PostgreSQL with read replicas
- D.Azure SQL Database (single database)
Why A: Azure SQL Database with active geo-replication (Option A) is the correct choice because it enables automatic failover to a secondary region in case of a regional outage, meeting the high availability requirement. Option B (Azure SQL Managed Instance with local redundancy) only provides local redundancy within a single region, not cross-region failover. Option C (Azure Database for PostgreSQL with read replicas) does not provide automatic failover; read replicas are for read scaling, not failover. Option D (Azure SQL Database single database) by default does not have automatic regional failover; active geo-replication is needed for that.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-900 exam.