Question 700
An Azure SQL operations team investigates: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. 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: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. The specific supported administrative response is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts. The technical risk is: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. Confirm the correction with: A simulated failure triggers the expected alert with actionable job identity, step and owner context.
The acceptance evidence for this incident (An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts.) is: A simulated failure triggers the expected alert with actionable job identity, step and owner context. It directly tests whether the remediation (Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Azure SQL resource deployment using bicep (4.2) would demonstrate or implement: A repeatable deployment produces the approved Azure SQL resource configuration and its change is reviewable. The case states: An auditor requests evidence of the last successful maintenance run and any unresolved failure alerts. The most direct paired action and test is: Monitor the success, duration and failures of SQL Agent, elastic jobs or Azure Automation tasks with appropriate platform-specific alerts.
Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. This choice can be useful for that problem, but it does not establish the Database task alerts and outcome monitoring (4.3) control being assessed here.
Azure powershell database automation (4.2) addresses another technical failure: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. The required paired action and test concerns Database task alerts and outcome monitoring (4.3); a passing result for this alternative could leave that requirement unresolved.