Question 370
An Azure SQL operations team investigates: A migration to Azure SQL needs a baseline for validating post-cutover query response times. 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 migration to Azure SQL needs a baseline for validating post-cutover query response times. The specific supported administrative response is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service. The technical risk is: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. Confirm the correction with: Before-and-after metrics for a comparable workload window show a measured effect on the requirement.
The acceptance evidence for this incident (A migration to Azure SQL needs a baseline for validating post-cutover query response times.) is: Before-and-after metrics for a comparable workload window show a measured effect on the requirement. It directly tests whether the remediation (Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Azure SQL compute and storage scaling (3.3) addresses another technical failure: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. The case states: A migration to Azure SQL needs a baseline for validating post-cutover query response times. The most direct paired action and test is: Capture representative CPU, IO, duration, wait and concurrency baselines across normal and peak workloads before changing the SQL service.
Resource governor workload classification (3.3) would demonstrate or implement: A workload classification test shows intended resource limits without starving high-priority connections. This case instead tests SQL workload performance baselining (3.1); the choice measures or changes another part of the system.
Azure monitor metrics and diagnostic settings (3.1) addresses another technical failure: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. The required paired action and test concerns SQL workload performance baselining (3.1); a passing result for this alternative could leave that requirement unresolved.