Question 850
An Azure SQL operations team investigates: A recovery rehearsal finds the secondary region is missing firewall rules and principals required by the group listener. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A recovery rehearsal finds the secondary region is missing firewall rules and principals required by the group listener.) is: A controlled failover redirects application connections through the group listener and maintains approved database membership. It directly tests whether the remediation (Use supported Azure SQL failover groups when coordinated failover of a set of databases and stable read-write or read-only listeners are required.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A recovery rehearsal finds the secondary region is missing firewall rules and principals required by the group listener. The specific supported administrative response is: Use supported Azure SQL failover groups when coordinated failover of a set of databases and stable read-write or read-only listeners are required. The technical risk is: Applications tied to a physical primary server hostname may fail after a regional switchover even when a secondary is healthy. Confirm the correction with: A controlled failover redirects application connections through the group listener and maintains approved database membership.
Incorrect Answers
Native restore sequence with norecovery and recovery (5.2) would demonstrate or implement: A rehearsed restore applies the intended complete backup chain and opens the database only after final RECOVERY. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A controlled failover redirects application connections through the group listener and maintains approved database membership.
SQL server backup and restore to azure blob storage (5.2) addresses another technical failure: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. This case instead tests Azure SQL failover groups and stable listener (5.3); the choice measures or changes another part of the system.
Monitoring replica health and lag across ha dr (5.3) addresses another technical failure: A replica shown as connected can still be too far behind or unhealthy to satisfy recovery objectives. The required paired action and test concerns Azure SQL failover groups and stable listener (5.3); a passing result for this alternative could leave that requirement unresolved.