Question 430
While validating an Azure workload, the security team finds: A single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements. Which safeguard would best prevent this issue from recurring?
Explanation
Correct Answer
This guardrail addresses backup multiuser authorization resource guard: Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. The prevention measure is: Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. “Match vault tier and key protection type to compliance requirements before key creation and migration” would address that alternative cause, not the condition in this question: critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary.
“Test policy assignment identities and post-remediation telemetry as part of baseline enforcement” responds to this separate finding: a DeployIfNotExists assignment evaluates related resources but needs appropriate assignment identity permissions and remediation for existing assets. This question instead needs “Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards”, so the alternative does not meet the stated condition.
Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period. “Require recovery drills and purge protection for Key Vault keys that protect production data” applies to that separate problem. The observed case is a single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements; choosing this alternative would address the wrong failure mode.