https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-sql#combining-bcdr-technologies-with-site-recovery
Basic Concept: This question tests high availability and disaster recovery design for Azure SQL, SQL Server on Azure VMs, and regional failure scenarios.
Why A is Correct: Azure Site Recovery is correct because it is the feature whose normal purpose matches the stated requirement. Azure Site Recovery is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. The scenario wording points to that specific behavior: You need to implement a disaster recovery solution that meets the following requirements: • Returns the solution to an operational state within 15 minutes of a failure • Can perform disaster recovery testing in an isolated environment • Minimizes administrativ
Why B is Wrong: a failover cluster instance (FCI) is part of the availability or recovery design space, but the correct choice must satisfy the specified failover, restore, quorum, RPO, or RTO requirement. It does not meet the failover, restore, quorum, or cross-region continuity target stated in the question, even if it is valid in a different availability design.
Why C is Wrong: Auto-failover groups provide managed geo-replication and listener-based failover for Azure SQL Database or Managed Instance, including automatic failover policies for regional outages. It handles a different resilience pattern and would not deliver the failover or recovery behavior required here.
Why D is Wrong: Active geo-replication creates readable secondary databases, but failover groups add the managed listener and automatic failover abstraction needed for application continuity at scale. It is not wrong technology in general, but it is the wrong HA/DR control for this scenario ' s failure model.
