Question 380
An Azure SQL operations team investigates: A service owner needs to distinguish compute saturation from general application front-end latency. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A service owner needs to distinguish compute saturation from general application front-end latency.) is: A reproducible resource event appears in the chosen metric or log destination and its threshold generates the intended alert. It directly tests whether the remediation (Use Azure Monitor metrics, suitable diagnostic settings, log destinations and alerts to observe Azure SQL resource health and capacity.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A service owner needs to distinguish compute saturation from general application front-end latency. The specific supported administrative response is: Use Azure Monitor metrics, suitable diagnostic settings, log destinations and alerts to observe Azure SQL resource health and capacity. The technical risk is: Platform metrics alone may miss a query-level root cause while unconfigured diagnostics leave gaps in incident history. Confirm the correction with: A reproducible resource event appears in the chosen metric or log destination and its threshold generates the intended alert.
Incorrect Answers
Database watcher monitoring and preview status (3.1) addresses another technical failure: Assuming a preview monitoring feature is generally available in every region or requires no permissions can break operational rollout. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A reproducible resource event appears in the chosen metric or log destination and its threshold generates the intended alert.
Deadlock detection and remediation (3.2) would demonstrate or implement: A concurrency test no longer produces the captured deadlock cycle and database correctness is preserved. The required paired action and test concerns Azure monitor metrics and diagnostic settings (3.1); a passing result for this alternative could leave that requirement unresolved.
Index maintenance and fragmentation evidence (3.3) addresses another technical failure: Unconditional rebuilds can create log IO and contention without meaningful query benefits. The paired-answer requirement concerns Azure monitor metrics and diagnostic settings (3.1); this alternative does not provide the matching intervention and separate acceptance evidence.