Question 640
An Azure SQL operations team investigates: A release system needs a noninteractive service identity to run a documented Azure CLI database action. 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 release system needs a noninteractive service identity to run a documented Azure CLI database action. The specific supported administrative response is: Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments. The technical risk is: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. Confirm the correction with: CLI output and an independent resource readback confirm the database was created with intended settings.
The acceptance evidence for this incident (A release system needs a noninteractive service identity to run a documented Azure CLI database action.) is: CLI output and an independent resource readback confirm the database was created with intended settings. It directly tests whether the remediation (Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. The case states: A release system needs a noninteractive service identity to run a documented Azure CLI database action. The most direct paired action and test is: Use Azure CLI with explicit account, subscription, resource-group and SQL database parameters to automate approved SQL deployments.
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. This case instead tests Azure cli SQL resource provisioning (4.2); the choice measures or changes another part of the system.
Elastic jobs across azure SQL databases (4.3) would demonstrate or implement: Elastic job execution history shows the approved step ran on all selected target databases and excluded unrelated tenants. The paired-answer requirement concerns Azure cli SQL resource provisioning (4.2); this alternative does not provide the matching intervention and separate acceptance evidence.