Question 590
An Azure SQL operations team investigates: A compliance team wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A compliance team wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions.) is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail. It directly tests whether the remediation (Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A compliance team wants to prove automated SQL tasks do not inherit unnecessary server-wide permissions. The specific supported administrative response is: Run SQL Server Agent job steps under appropriately scoped credentials or supported proxies and review permissions to external resources. The technical risk is: Using sysadmin for every automation step or leaving network shares inaccessible can create security and reliability failures. Confirm the correction with: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.
Incorrect Answers
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. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: The job completes using a least-privilege execution principal while attempts to access unapproved paths fail.
SQL server agent maintenance job schedules (4.1) addresses another technical failure: Unscheduled manual tasks or unsupported agent assumptions can leave maintenance undone or jobs never executed. This choice can be useful for that problem, but it does not establish the SQL agent execution context and proxy permissions (4.1) control being assessed here.
Elastic job credential and target security (4.3) would demonstrate or implement: A controlled job connects only to intended target databases, completes allowed statements and is denied unapproved objects. The required paired action and test concerns SQL agent execution context and proxy permissions (4.1); a passing result for this alternative could leave that requirement unresolved.