Question 630
An Azure SQL operations team investigates: A compliance team requires logged configuration changes instead of unaudited manual portal edits. 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 requires logged configuration changes instead of unaudited manual portal edits.) is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs. It directly tests whether the remediation (Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A compliance team requires logged configuration changes instead of unaudited manual portal edits. The specific supported administrative response is: Use supported Az PowerShell cmdlets or Azure Resource Manager calls with secured identities for repeated SQL resource configuration operations. The technical risk is: Scripts that depend on a person's interactive credentials or omit subscription context can change the wrong environment. Confirm the correction with: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.
Incorrect Answers
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. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: A scheduled or reviewed PowerShell run targets the intended subscription and SQL resources with expected change logs.
Infrastructure drift and declarative reconciliation (4.2) addresses another technical failure: Untracked manual overrides can break reproducibility and cause security configuration drift between environments. This choice can be useful for that problem, but it does not establish the Azure powershell database automation (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 Azure powershell database automation (4.2); the choice measures or changes another part of the system.