Question 510
An Azure SQL operations team investigates: A DBA plans online-capable index maintenance after evaluating edition support and operational impact. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A DBA plans online-capable index maintenance after evaluating edition support and operational impact.) is: Maintenance completes within the window and index health and real query performance meet measured expectations. It directly tests whether the remediation (Schedule appropriate index reorganize or rebuild activity only when measured fragmentation or workload needs justify it and the platform supports the operation.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A DBA plans online-capable index maintenance after evaluating edition support and operational impact. The specific supported administrative response is: Schedule appropriate index reorganize or rebuild activity only when measured fragmentation or workload needs justify it and the platform supports the operation. The technical risk is: Unconditional rebuilds can create log IO and contention without meaningful query benefits. Confirm the correction with: Maintenance completes within the window and index health and real query performance meet measured expectations.
Incorrect Answers
Intelligent insights for SQL performance diagnosis (3.2) would demonstrate or implement: An observed insight matches measured query or resource behavior and the targeted remediation improves a subsequent sample. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: Maintenance completes within the window and index health and real query performance meet measured expectations.
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 choice can be useful for that problem, but it does not establish the Index maintenance and fragmentation evidence (3.3) control being assessed here.
Azure SQL compute and storage scaling (3.3) addresses another technical failure: Increasing vCores blindly may not solve throttled log IO or storage bottlenecks and scaling can cause transient failovers. The paired-answer requirement concerns Index maintenance and fragmentation evidence (3.3); this alternative does not provide the matching intervention and separate acceptance evidence.