Question 560
An Azure SQL operations team investigates: A service owner needs to validate the cost and performance trade-offs of a higher Azure SQL service objective. 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 service owner needs to validate the cost and performance trade-offs of a higher Azure SQL service objective. The specific supported administrative response is: Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations. The technical risk is: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. Confirm the correction with: Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective.
The acceptance evidence for this incident (A service owner needs to validate the cost and performance trade-offs of a higher Azure SQL service objective.) is: Before-and-after workload metrics, capacity headroom and connection behavior confirm that the change meets its objective. It directly tests whether the remediation (Resize supported Azure SQL compute and storage service objectives based on sustained utilization, latency and downtime considerations.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
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. This choice can be useful for that problem, but it does not establish the Azure SQL compute and storage scaling (3.3) control being assessed here.
Query store performance regressions (3.2) addresses another technical failure: Changing server compute before checking a new inefficient execution plan can mask a query-level regression. This case instead tests Azure SQL compute and storage scaling (3.3); the choice measures or changes another part of the system.
Statistics maintenance and cardinality accuracy (3.3) addresses another technical failure: Stale histograms can lead to poor row estimates and inefficient plan choices even with appropriate indexes. The paired-answer requirement concerns Azure SQL compute and storage scaling (3.3); this alternative does not provide the matching intervention and separate acceptance evidence.