Question 420
An Azure SQL operations team investigates: A blocking incident has ended and current DMVs alone cannot reconstruct the historical event without other capture. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A blocking incident has ended and current DMVs alone cannot reconstruct the historical event without other capture.) is: Relevant DMV results isolate the expected session or resource condition and are consistent with current workload tests. It directly tests whether the remediation (Use supported dynamic management views to inspect active sessions, waits, query resource usage and database health within documented permission boundaries.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A blocking incident has ended and current DMVs alone cannot reconstruct the historical event without other capture. The specific supported administrative response is: Use supported dynamic management views to inspect active sessions, waits, query resource usage and database health within documented permission boundaries. The technical risk is: A narrow resource graph cannot identify the specific running statements or session-level wait chains involved in an outage. Confirm the correction with: Relevant DMV results isolate the expected session or resource condition and are consistent with current workload tests.
Incorrect Answers
Intelligent insights for SQL performance diagnosis (3.2) addresses another technical failure: Automatically generated diagnosis may identify a symptom but cannot replace verification of the actual workload and cause. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: Relevant DMV results isolate the expected session or resource condition and are consistent with current workload tests.
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. This choice can be useful for that problem, but it does not establish the SQL monitoring with dmvs (3.1) control being assessed here.
Execution plan scans and cardinality estimation (3.2) would demonstrate or implement: The revised plan and measured reads show the intended operator change with correct query results. The paired-answer requirement concerns SQL monitoring with dmvs (3.1); this alternative does not provide the matching intervention and separate acceptance evidence.