Question 20
An Azure SQL operations team investigates: An enterprise wants managed patching but needs features closer to boxed SQL Server than a logical database offers. 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: An enterprise wants managed patching but needs features closer to boxed SQL Server than a logical database offers. The specific supported administrative response is: Choose Azure SQL Managed Instance when managed PaaS with high SQL Server instance feature compatibility is required, after checking supported features. The technical risk is: Selecting single-database PaaS for SQL Agent or instance-centered dependencies creates costly compatibility rework. Confirm the correction with: A migration rehearsal demonstrates required supported instance-level jobs and dependent database operations on the managed instance.
The acceptance evidence for this incident (An enterprise wants managed patching but needs features closer to boxed SQL Server than a logical database offers.) is: A migration rehearsal demonstrates required supported instance-level jobs and dependent database operations on the managed instance. It directly tests whether the remediation (Choose Azure SQL Managed Instance when managed PaaS with high SQL Server instance feature compatibility is required, after checking supported features.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Azure arc-enabled SQL server inventory (1.1) addresses another technical failure: Without consistent hybrid inventory, patch and configuration state can be missed across data centers. The case states: An enterprise wants managed patching but needs features closer to boxed SQL Server than a logical database offers. The most direct paired action and test is: Choose Azure SQL Managed Instance when managed PaaS with high SQL Server instance feature compatibility is required, after checking supported features.
Columnstore and row compression decisions (1.2) addresses another technical failure: The wrong compression strategy can increase CPU overhead or degrade point-lookup performance despite smaller storage. The required paired action and test concerns Azure SQL managed instance compatibility (1.1); a passing result for this alternative could leave that requirement unresolved.
Azure SQL business critical tier selection (1.2) would demonstrate or implement: Benchmark results show the chosen service objective meets transaction latency and availability targets within budget. The paired-answer requirement concerns Azure SQL managed instance compatibility (1.1); this alternative does not provide the matching intervention and separate acceptance evidence.