Question 690
An Azure SQL operations team investigates: An organization needs a repeatable Azure SQL automation task that produces protected execution history. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (An organization needs a repeatable Azure SQL automation task that produces protected execution history.) is: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources. It directly tests whether the remediation (Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: An organization needs a repeatable Azure SQL automation task that produces protected execution history. The specific supported administrative response is: Use Azure Automation runbooks with managed identity and appropriate module support for approved SQL administrative tasks. The technical risk is: Automation code containing embedded secrets or unsupported legacy Run As account patterns creates security and maintenance risk. Confirm the correction with: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.
Incorrect Answers
Infrastructure drift and declarative reconciliation (4.2) would demonstrate or implement: A drift check identifies a test manual change and a reviewed pipeline restores the approved state. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A scheduled runbook uses its managed identity, writes an auditable outcome and changes only authorized SQL resources.
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 case instead tests Azure automation SQL runbooks and managed identities (4.3); the choice measures or changes another part of the system.
SQL agent execution context and proxy permissions (4.1) addresses another technical failure: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. The required paired action and test concerns Azure automation SQL runbooks and managed identities (4.3); a passing result for this alternative could leave that requirement unresolved.