Question 660
An Azure SQL operations team investigates: A team wants to prevent a nightly automation run from reverting legitimate but undocumented hotfixes without review. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A team wants to prevent a nightly automation run from reverting legitimate but undocumented hotfixes without review.) is: A drift check identifies a test manual change and a reviewed pipeline restores the approved state. It directly tests whether the remediation (Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A team wants to prevent a nightly automation run from reverting legitimate but undocumented hotfixes without review. The specific supported administrative response is: Compare deployed Azure SQL resources with approved IaC definitions and reconcile changes through controlled pipeline updates. The technical risk is: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. Confirm the correction with: A drift check identifies a test manual change and a reviewed pipeline restores the approved state.
Incorrect Answers
SQL agent execution context and proxy permissions (4.1) would demonstrate or implement: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A drift check identifies a test manual change and a reviewed pipeline restores the approved state.
SQL agent job alerts and operator notifications (4.1) addresses another technical failure: A job can fail repeatedly without incident response if its failure status is not routed to a responsible operator. This choice can be useful for that problem, but it does not establish the Infrastructure drift and declarative reconciliation (4.2) control being assessed here.
Deployment operation logs and failed arm resources (4.2) addresses another technical failure: Blind retries without checking deployment errors can reproduce the same missing-permission or subnet issue. The required paired action and test concerns Infrastructure drift and declarative reconciliation (4.2); a passing result for this alternative could leave that requirement unresolved.