Reference:
https://docs.microsoft.com/en-us/azure/azure-sql/database/auto-failover-group-overview?tabs=azure- powershell#best-practices-for-sql-database
https://docs.microsoft.com/en-us/azure/azure-sql/database/failover-group-add-single-database-tutorial?
tabs=azure-portal
Basic Concept: This question tests high availability and disaster recovery design for Azure SQL, SQL Server on Azure VMs, and regional failure scenarios.
Why B and C is Correct: 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. In this scenario, the important constraint is: You need to ensure that users can connect to DB1 in the event of an Azure regional outage. From the properties of Server1 add a failover group. satisfies that constraint without adding an unrelated service or manual process. Create a new Azure SQL Database server named Server2.
matches the expected DP-300 administration action. Create a new Azure SQL Database server named Server2. 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 question is not asking for a general Azure capability; it is asking for the feature that produces this result: You need to ensure that users can connect to DB1 in the event of an Azure regional outage.
Why A 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 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 D is Wrong: From the properties of Server1 configure retention for DB1 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 E is Wrong: Create a new Azure SQL Database instance named DB2. 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 handles a different resilience pattern and would not deliver the failover or recovery behavior required here.