Question 60
An Azure SQL operations team investigates: A database move waits for explicit completion after seeding and the DBA must plan final cutover within the supported window. 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 database move waits for explicit completion after seeding and the DBA must plan final cutover within the supported window. The specific supported administrative response is: Use supported online database copy or move between SQL managed instances in the same Azure region and tenant after checking permissions, network connectivity and update policies. The technical risk is: A copy preserves the source database after completion, whereas an approved move removes the source; wrong operation choices or incompatible update policies can interrupt work. Confirm the correction with: An approved copy leaves both independent databases online, or a controlled move finishes with the target writable and the source removed as intended.
The acceptance evidence for this incident (A database move waits for explicit completion after seeding and the DBA must plan final cutover within the supported window.) is: An approved copy leaves both independent databases online, or a controlled move finishes with the target writable and the source removed as intended. It directly tests whether the remediation (Use supported online database copy or move between SQL managed instances in the same Azure region and tenant after checking permissions, network connectivity and update policies.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Offline migration and validated cutover (1.3) addresses another technical failure: Restoring from a single old backup without stopping writes or validation can lose committed changes. The case states: A database move waits for explicit completion after seeding and the DBA must plan final cutover within the supported window. The most direct paired action and test is: Use supported online database copy or move between SQL managed instances in the same Azure region and tenant after checking permissions, network connectivity and update policies.
Table partitioning for large tables (1.2) addresses another technical failure: Partitioning without a matching access pattern or maintenance plan can complicate administration without improving queries. This case instead tests Azure SQL managed instance database copy and move (1.3); the choice measures or changes another part of the system.
Azure SQL database platform fit (1.1) would demonstrate or implement: A deployment assessment confirms all required features work without managing SQL Server operating system or instance maintenance. The required paired action and test concerns Azure SQL managed instance database copy and move (1.3); a passing result for this alternative could leave that requirement unresolved.