Question 840
An Azure SQL operations team investigates: A multi-database application is configured with independent geo-replicas but no coordinated failover design. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The reported Azure SQL or SQL Server condition is: A multi-database application is configured with independent geo-replicas but no coordinated failover design. The specific supported administrative response is: Configure active geo-replication for supported Azure SQL Database individual databases to create readable secondaries and initiate supported failover. The technical risk is: An asynchronous geo-secondary may lag behind the primary and individual database failover does not automatically coordinate a multi-database application. Confirm the correction with: Replication status and controlled failover tests show the chosen database can be read on the secondary and promoted with documented data-loss expectations.
The acceptance evidence for this incident (A multi-database application is configured with independent geo-replicas but no coordinated failover design.) is: Replication status and controlled failover tests show the chosen database can be read on the secondary and promoted with documented data-loss expectations. It directly tests whether the remediation (Configure active geo-replication for supported Azure SQL Database individual databases to create readable secondaries and initiate supported failover.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Disaster recovery runbook and rehearsal (5.1) addresses another technical failure: An untested disaster recovery plan may fail due to stale credentials, missing DNS or unfamiliar operational steps. This choice can be useful for that problem, but it does not establish the Azure SQL database active geo-replication (5.3) control being assessed here.
Azure SQL failover groups and stable listener (5.3) addresses another technical failure: Applications tied to a physical primary server hostname may fail after a regional switchover even when a secondary is healthy. This case instead tests Azure SQL database active geo-replication (5.3); the choice measures or changes another part of the system.
Geo-restore from replicated azure SQL backups (5.2) would demonstrate or implement: A controlled alternate-region restore achieves documented recovery time and verifies expected records within the backup RPO. The paired-answer requirement concerns Azure SQL database active geo-replication (5.3); this alternative does not provide the matching intervention and separate acceptance evidence.