Question 490
An Azure SQL operations team investigates: An application team closes a detected issue without measuring whether latency recovered. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (An application team closes a detected issue without measuring whether latency recovered.) is: An observed insight matches measured query or resource behavior and the targeted remediation improves a subsequent sample. It directly tests whether the remediation (Use supported Azure SQL Intelligent Insights findings as evidence to prioritize query or resource investigations, with follow-up validation.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: An application team closes a detected issue without measuring whether latency recovered. The specific supported administrative response is: Use supported Azure SQL Intelligent Insights findings as evidence to prioritize query or resource investigations, with follow-up validation. The technical risk is: Automatically generated diagnosis may identify a symptom but cannot replace verification of the actual workload and cause. Confirm the correction with: An observed insight matches measured query or resource behavior and the targeted remediation improves a subsequent sample.
Incorrect Answers
SQL monitoring with dmvs (3.1) would demonstrate or implement: Relevant DMV results isolate the expected session or resource condition and are consistent with current workload tests. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: An observed insight matches measured query or resource behavior and the targeted remediation improves a subsequent sample.
Deadlock detection and remediation (3.2) addresses another technical failure: A deadlock is a cyclic lock dependency, so increasing lock timeout alone does not remove the conflicting access pattern. This choice can be useful for that problem, but it does not establish the Intelligent insights for SQL performance diagnosis (3.2) control being assessed here.
Azure SQL automatic tuning governance (3.3) addresses another technical failure: Applying optimizer recommendations without observing workload impact can introduce extra index overhead or unstable plans. The required paired action and test concerns Intelligent insights for SQL performance diagnosis (3.2); a passing result for this alternative could leave that requirement unresolved.