Question 650
An Azure SQL operations team investigates: An automated rollout exceeds resource quotas and the operator needs to identify the rejected operation. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (An automated rollout exceeds resource quotas and the operator needs to identify the rejected operation.) is: A corrected deployment operation completes and the intended resources and dependencies appear in readback. It directly tests whether the remediation (Inspect Azure deployment operation records, resource-provider errors and dependencies before rerunning failed SQL infrastructure changes.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: An automated rollout exceeds resource quotas and the operator needs to identify the rejected operation. The specific supported administrative response is: Inspect Azure deployment operation records, resource-provider errors and dependencies before rerunning failed SQL infrastructure changes. The technical risk is: Blind retries without checking deployment errors can reproduce the same missing-permission or subnet issue. Confirm the correction with: A corrected deployment operation completes and the intended resources and dependencies appear in readback.
Incorrect Answers
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 case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A corrected deployment operation completes and the intended resources and dependencies appear in readback.
Fabric SQL database pipelines and recurring tasks (4.3) would demonstrate or implement: The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience. This choice can be useful for that problem, but it does not establish the Deployment operation logs and failed arm resources (4.2) control being assessed here.
Maintaining job schedules across failover (4.1) addresses another technical failure: A database can fail over successfully while instance-level jobs on the new primary remain absent or disabled. This case instead tests Deployment operation logs and failed arm resources (4.2); the choice measures or changes another part of the system.