Question 610
An Azure SQL operations team investigates: A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules.) is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes. It directly tests whether the remediation (Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A disaster-recovery plan includes the database connection string but omits job owners, notifications and schedules. The specific supported administrative response is: Include supported SQL Agent jobs, credentials and notifications in HA/DR runbooks and validate execution after failover. The technical risk is: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. Confirm the correction with: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.
Incorrect Answers
Azure automation SQL runbooks and managed identities (4.3) addresses another technical failure: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A documented failover rehearsal shows required jobs exist, are correctly enabled and do not run twice on both nodes.
Azure SQL resource deployment using bicep (4.2) would demonstrate or implement: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable. This choice can be useful for that problem, but it does not establish the Maintaining job schedules across failover (4.1) control being assessed here.
SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This case instead tests Maintaining job schedules across failover (4.1); the choice measures or changes another part of the system.