Question 410
An Azure SQL operations team investigates: A team compares cumulative historical wait stats without accounting for uptime or sample interval. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A team compares cumulative historical wait stats without accounting for uptime or sample interval.) is: The selected remediation measurably reduces the relevant observed wait or bottleneck under comparable load. It directly tests whether the remediation (Correlate SQL wait types, CPU, memory, storage and workload metrics before diagnosing a database performance bottleneck.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A team compares cumulative historical wait stats without accounting for uptime or sample interval. The specific supported administrative response is: Correlate SQL wait types, CPU, memory, storage and workload metrics before diagnosing a database performance bottleneck. The technical risk is: Treating every high wait counter as CPU pressure can prompt ineffective scaling or index changes. Confirm the correction with: The selected remediation measurably reduces the relevant observed wait or bottleneck under comparable load.
Incorrect Answers
Index design for selective oltp queries (3.2) would demonstrate or implement: A representative query shows lower logical reads or execution time without unacceptable write overhead. This choice can be useful for that problem, but it does not establish the Wait statistics and resource bottleneck interpretation (3.1) control being assessed here.
Execution plan scans and cardinality estimation (3.2) addresses another technical failure: Choosing an index solely from table size without seeing the predicate and plan can waste resources. The required paired action and test concerns Wait statistics and resource bottleneck interpretation (3.1); a passing result for this alternative could leave that requirement unresolved.
SQL workload performance baselining (3.1) addresses another technical failure: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. The paired-answer requirement concerns Wait statistics and resource bottleneck interpretation (3.1); this alternative does not provide the matching intervention and separate acceptance evidence.