Question 520
An Azure SQL operations team investigates: A compliance team wants documented evidence of integrity verification appropriate to each SQL hosting model. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A compliance team wants documented evidence of integrity verification appropriate to each SQL hosting model.) is: Documented integrity verification and recovery readiness produce actionable clean or investigated results. It directly tests whether the remediation (Use supported DBCC CHECKDB or managed-platform integrity verification approaches appropriate to the SQL deployment and recovery plan.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A compliance team wants documented evidence of integrity verification appropriate to each SQL hosting model. The specific supported administrative response is: Use supported DBCC CHECKDB or managed-platform integrity verification approaches appropriate to the SQL deployment and recovery plan. The technical risk is: A successful backup or query does not by itself prove every database page and relationship is consistent. Confirm the correction with: Documented integrity verification and recovery readiness produce actionable clean or investigated results.
Incorrect Answers
Resource governor workload classification (3.3) addresses another technical failure: Applying an instance feature to an unsupported Azure SQL database tier or using incorrect classifiers can fail or throttle critical users. This case instead tests Database integrity checks and consistency (3.3); the choice measures or changes another part of the system.
Query store performance regressions (3.2) would demonstrate or implement: Query Store shows the selected query's plan and runtime behavior returning to baseline after a validated change. The required paired action and test concerns Database integrity checks and consistency (3.3); 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 Database integrity checks and consistency (3.3); this alternative does not provide the matching intervention and separate acceptance evidence.