Question 830
An Azure SQL operations team investigates: A DBA wants to compare geo-restore recovery duration with an established failover group for a critical database. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A DBA wants to compare geo-restore recovery duration with an established failover group for a critical database.) is: A controlled alternate-region restore achieves documented recovery time and verifies expected records within the backup RPO. It directly tests whether the remediation (Use supported Azure SQL geo-restore from geo-redundant automated backups when live secondary replication is not configured, accepting its RPO/RTO limits.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A DBA wants to compare geo-restore recovery duration with an established failover group for a critical database. The specific supported administrative response is: Use supported Azure SQL geo-restore from geo-redundant automated backups when live secondary replication is not configured, accepting its RPO/RTO limits. The technical risk is: Geo-restore typically has longer recovery and potentially older restore points than a continuously synchronized geo-secondary. Confirm the correction with: A controlled alternate-region restore achieves documented recovery time and verifies expected records within the backup RPO.
Incorrect Answers
SQL server log shipping for warm standby (5.3) addresses another technical failure: A missing copy job or broken log chain can leave the standby many hours behind despite successful primary backups. This choice can be useful for that problem, but it does not establish the Geo-restore from replicated azure SQL backups (5.2) control being assessed here.
Ha dr design from rpo and rto (5.1) would demonstrate or implement: A failure rehearsal measures actual recovery time and data divergence against documented RTO and RPO targets. This case instead tests Geo-restore from replicated azure SQL backups (5.2); the choice measures or changes another part of the system.
Long-term retention for compliance backups (5.2) addresses another technical failure: Ordinary short-term recovery retention cannot satisfy multi-year records preservation requirements. The paired-answer requirement concerns Geo-restore from replicated azure SQL backups (5.2); this alternative does not provide the matching intervention and separate acceptance evidence.