Question 400
An Azure SQL operations team investigates: An incident report needs error details and durations for a short defined troubleshooting window. 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 incident report needs error details and durations for a short defined troubleshooting window. The specific supported administrative response is: Configure a narrowly scoped Extended Events session to capture relevant SQL statements, waits or errors with safe target storage and retention. The technical risk is: Heavy unrestricted tracing can consume resources and bury the evidence needed for a specific incident. Confirm the correction with: A controlled workload produces only the expected events and capture overhead stays within approved thresholds.
The acceptance evidence for this incident (An incident report needs error details and durations for a short defined troubleshooting window.) is: A controlled workload produces only the expected events and capture overhead stays within approved thresholds. It directly tests whether the remediation (Configure a narrowly scoped Extended Events session to capture relevant SQL statements, waits or errors with safe target storage and retention.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Database integrity checks and consistency (3.3) would demonstrate or implement: Documented integrity verification and recovery readiness produce actionable clean or investigated results. This choice can be useful for that problem, but it does not establish the Extended events performance capture (3.1) 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. This case instead tests Extended events performance capture (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 Extended events performance capture (3.1); a passing result for this alternative could leave that requirement unresolved.