Question 670
An Azure SQL operations team investigates: A maintenance script should run against one Azure SQL database without granting access to all customers. 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: A maintenance script should run against one Azure SQL database without granting access to all customers. The specific supported administrative response is: Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases. The technical risk is: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. Confirm the correction with: Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants.
The acceptance evidence for this incident (A maintenance script should run against one Azure SQL database without granting access to all customers.) is: Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants. It directly tests whether the remediation (Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Deployment operation logs and failed arm resources (4.2) would demonstrate or implement: A corrected deployment operation completes and the intended resources and dependencies appear in readback. The case states: A maintenance script should run against one Azure SQL database without granting access to all customers. The most direct paired action and test is: Use Azure SQL Database elastic jobs with an agent, job database, target groups and schedule for T-SQL tasks across one or many databases.
Azure SQL resource deployment using bicep (4.2) addresses another technical failure: Manual production configuration can drift from tested resource sizing, networking and backup settings. This case instead tests Elastic jobs across azure SQL databases (4.3); the choice measures or changes another part of the system.
Database task alerts and outcome monitoring (4.3) addresses another technical failure: A schedule existing in configuration does not prove its SQL operation executed or completed successfully. The required paired action and test concerns Elastic jobs across azure SQL databases (4.3); a passing result for this alternative could leave that requirement unresolved.