Question 870
An Azure SQL operations team investigates: A recovery runbook must distinguish clustered instance failover from moving an individual Always On 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 recovery runbook must distinguish clustered instance failover from moving an individual Always On database.) is: A node failure transfers the clustered SQL instance role to the healthy node and the virtual client name remains available. It directly tests whether the remediation (Use a supported SQL Server failover cluster instance design with compatible shared storage and cluster/network configuration when instance-level high availability is required.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A recovery runbook must distinguish clustered instance failover from moving an individual Always On database. The specific supported administrative response is: Use a supported SQL Server failover cluster instance design with compatible shared storage and cluster/network configuration when instance-level high availability is required. The technical risk is: An availability group and a failover cluster instance protect different scopes; a cluster instance requires supported shared-storage and cluster prerequisites. Confirm the correction with: A node failure transfers the clustered SQL instance role to the healthy node and the virtual client name remains available.
Incorrect Answers
Long-term retention for compliance backups (5.2) would demonstrate or implement: Retention inventory and a restore rehearsal show the required historic backup can still be accessed within policy. This choice can be useful for that problem, but it does not establish the SQL server failover cluster instances on azure vms (5.3) control being assessed here.
Always on availability groups on azure SQL vms (5.3) addresses another technical failure: Replica databases may synchronize yet applications remain unavailable if quorum, listener configuration or failover mode is wrong. This case instead tests SQL server failover cluster instances on azure vms (5.3); the choice measures or changes another part of the system.
Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. The paired-answer requirement concerns SQL server failover cluster instances on azure vms (5.3); this alternative does not provide the matching intervention and separate acceptance evidence.