Question 740
An Azure SQL operations team investigates: A new cloud DR host has database files yet inbound firewall rules do not permit the dependent application. 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 new cloud DR host has database files yet inbound firewall rules do not permit the dependent application. The specific supported administrative response is: Plan hybrid SQL Server availability and disaster recovery with supported replication, network, identity and failover mechanisms for both sites. The technical risk is: Database replication alone does not ensure client routing, SQL Agent jobs, logins or DNS work after hybrid failover. Confirm the correction with: A full end-to-end exercise brings up application clients, required principals and operational jobs on the secondary site.
The acceptance evidence for this incident (A new cloud DR host has database files yet inbound firewall rules do not permit the dependent application.) is: A full end-to-end exercise brings up application clients, required principals and operational jobs on the secondary site. It directly tests whether the remediation (Plan hybrid SQL Server availability and disaster recovery with supported replication, network, identity and failover mechanisms for both sites.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Azure SQL database active geo-replication (5.3) would demonstrate or implement: Replication status and controlled failover tests show the chosen database can be read on the secondary and promoted with documented data-loss expectations. The case states: A new cloud DR host has database files yet inbound firewall rules do not permit the dependent application. The most direct paired action and test is: Plan hybrid SQL Server availability and disaster recovery with supported replication, network, identity and failover mechanisms for both sites.
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. This choice can be useful for that problem, but it does not establish the Hybrid SQL server dr topology planning (5.1) control being assessed here.
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 case instead tests Hybrid SQL server dr topology planning (5.1); the choice measures or changes another part of the system.