DP-300 · Question #314
You have an Azure SQL database. You need to implement a disaster recovery solution that meets the following requirements: - Minimizes how long it takes to recover the database if a datacenter fails…
The correct answer is C. auto-failover groups. Explanation Auto-failover groups (Option C) are correct because they provide automatic, policy-driven failover for Azure SQL databases with minimal administrative effort - when a datacenter failure is detected, failover happens automatically without manual intervention, and the…
Question
Options
- AAzure Site Recovery
- Bactive geo-replication
- Cauto-failover groups
- DAzure Backup
How the community answered
(33 responses)- A6% (2)
- B9% (3)
- C82% (27)
- D3% (1)
Explanation
Explanation
Auto-failover groups (Option C) are correct because they provide automatic, policy-driven failover for Azure SQL databases with minimal administrative effort - when a datacenter failure is detected, failover happens automatically without manual intervention, and the secondary database becomes readable/writable almost immediately, minimizing recovery time.
Azure Site Recovery (A) is designed for IaaS workloads like virtual machines, not specifically optimized for Azure SQL PaaS databases, making it the wrong tool for this scenario. Active geo-replication (B) does replicate your database to another region and minimizes recovery time, but it requires manual failover initiation, which increases administrative effort and doesn't meet the automation requirement. Azure Backup (D) focuses on point-in-time restore and backup retention, which has significantly longer recovery times (RPO/RTO) and is not suitable for rapid datacenter-failure recovery.
Memory Tip: Think of it this way - Active geo-replication = manual switch, Auto-failover groups = automatic switch. Whenever an exam question mentions both minimizing recovery time and minimizing administrative effort for Azure SQL, "auto" in auto-failover groups is your hint that automation (and less admin work) is built right into the name!
Topics
Community Discussion
No community discussion yet for this question.