Question 760
An Azure SQL operations team investigates: A DBA wants to distinguish normal read scale-out from actual disaster recovery functionality. 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 distinguish normal read scale-out from actual disaster recovery functionality.) is: Representative read and write tests confirm intended routing before and after a planned role change. It directly tests whether the remediation (Select supported read replicas and routing according to whether reporting should offload reads or the business requires writable primary failover.) 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 distinguish normal read scale-out from actual disaster recovery functionality. The specific supported administrative response is: Select supported read replicas and routing according to whether reporting should offload reads or the business requires writable primary failover. The technical risk is: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. Confirm the correction with: Representative read and write tests confirm intended routing before and after a planned role change.
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. This case instead tests Read-scale replicas versus writable ha requirements (5.1); the choice measures or changes another part of the system.
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 required paired action and test concerns Read-scale replicas versus writable ha requirements (5.1); a passing result for this alternative could leave that requirement unresolved.
Automated point-in-time restore for azure SQL (5.2) would demonstrate or implement: The restored database contains records consistent with the selected timestamp and application validation passes. The paired-answer requirement concerns Read-scale replicas versus writable ha requirements (5.1); this alternative does not provide the matching intervention and separate acceptance evidence.