Question 860
An Azure SQL operations team investigates: A forced failure leaves an availability group database unavailable and operators must inspect replica and cluster health. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A forced failure leaves an availability group database unavailable and operators must inspect replica and cluster health.) is: A planned replica failover preserves database accessibility through the listener and reports expected synchronization health. It directly tests whether the remediation (Configure supported SQL Server Always On availability groups on Azure VMs with appropriate Windows or Linux cluster prerequisites, endpoints and listener routing.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A forced failure leaves an availability group database unavailable and operators must inspect replica and cluster health. The specific supported administrative response is: Configure supported SQL Server Always On availability groups on Azure VMs with appropriate Windows or Linux cluster prerequisites, endpoints and listener routing. The technical risk is: Replica databases may synchronize yet applications remain unavailable if quorum, listener configuration or failover mode is wrong. Confirm the correction with: A planned replica failover preserves database accessibility through the listener and reports expected synchronization health.
Incorrect Answers
Hybrid SQL server dr topology planning (5.1) addresses another technical failure: Database replication alone does not ensure client routing, SQL Agent jobs, logins or DNS work after hybrid failover. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A planned replica failover preserves database accessibility through the listener and reports expected synchronization health.
SQL server backup and restore to azure blob storage (5.2) would demonstrate or implement: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials. This choice can be useful for that problem, but it does not establish the Always on availability groups on azure SQL vms (5.3) control being assessed here.
Azure SQL database active geo-replication (5.3) addresses another technical failure: An asynchronous geo-secondary may lag behind the primary and individual database failover does not automatically coordinate a multi-database application. The paired-answer requirement concerns Always on availability groups on azure SQL vms (5.3); this alternative does not provide the matching intervention and separate acceptance evidence.