Question 880
An Azure SQL operations team investigates: A post-migration cutover completes but the old data center still serves writes because failback ownership was not defined. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A post-migration cutover completes but the old data center still serves writes because failback ownership was not defined.) is: A tested MI continuity path preserves approved workload connectivity and reports the intended role and synchronization state. It directly tests whether the remediation (Evaluate supported Azure SQL Managed Instance failover or Managed Instance link capabilities for compatible hybrid and cloud continuity scenarios.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A post-migration cutover completes but the old data center still serves writes because failback ownership was not defined. The specific supported administrative response is: Evaluate supported Azure SQL Managed Instance failover or Managed Instance link capabilities for compatible hybrid and cloud continuity scenarios. The technical risk is: Assuming managed instance deployment includes every SQL Server high-availability mechanism without configuration can leave hybrid failback gaps. Confirm the correction with: A tested MI continuity path preserves approved workload connectivity and reports the intended role and synchronization state.
Incorrect Answers
Hybrid SQL server dr topology planning (5.1) would demonstrate or implement: A full end-to-end exercise brings up application clients, required principals and operational jobs on the secondary site. This choice can be useful for that problem, but it does not establish the SQL managed instance failover and link design (5.3) control being assessed here.
Azure SQL failover groups and stable listener (5.3) addresses another technical failure: Applications tied to a physical primary server hostname may fail after a regional switchover even when a secondary is healthy. This case instead tests SQL managed instance failover and link design (5.3); the choice measures or changes another part of the system.
SQL server backup and restore to azure blob storage (5.2) addresses another technical failure: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. The paired-answer requirement concerns SQL managed instance failover and link design (5.3); this alternative does not provide the matching intervention and separate acceptance evidence.