Question 430
An Azure SQL operations team investigates: A developer changes one predicate but historical query performance evidence remains available in Query Store. 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: A developer changes one predicate but historical query performance evidence remains available in Query Store. The specific supported administrative response is: Use Query Store runtime history and plan records to identify regressed queries and consider supported plan forcing when justified. The technical risk is: Changing server compute before checking a new inefficient execution plan can mask a query-level regression. Confirm the correction with: Query Store shows the selected query's plan and runtime behavior returning to baseline after a validated change.
The acceptance evidence for this incident (A developer changes one predicate but historical query performance evidence remains available in Query Store.) is: Query Store shows the selected query's plan and runtime behavior returning to baseline after a validated change. It directly tests whether the remediation (Use Query Store runtime history and plan records to identify regressed queries and consider supported plan forcing when justified.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
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 case states: A developer changes one predicate but historical query performance evidence remains available in Query Store. The most direct paired action and test is: Use Query Store runtime history and plan records to identify regressed queries and consider supported plan forcing when justified.
Azure SQL compute and storage scaling (3.3) would demonstrate or implement: Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective. The required paired action and test concerns Query store performance regressions (3.2); a passing result for this alternative could leave that requirement unresolved.
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 paired-answer requirement concerns Query store performance regressions (3.2); this alternative does not provide the matching intervention and separate acceptance evidence.