Despite carefully assigned permissions, a subscription owner could still accidentally delete a critical resource because their role already grants delete rights. Which feature prevents the resource from being deleted even by an owner, independent of their assigned permissions?
- AAzure RBAC, which already grants an owner permission to delete the resource
- BAzure Policy, which governs configuration compliance rather than deletion
- CMicrosoft Defender for Cloud, which manages security posture across resources
- DA resource lock, which blocks the action even for an owner of the resource Correct
Why A is wrong: Azure RBAC defines what an owner is allowed to do, which is relevant to access, but an owner already holds delete permission, so RBAC alone does nothing to stop the accidental deletion.
Why B is wrong: Azure Policy enforces rules on how resources are configured, which is governance, but it evaluates compliance rather than protecting an existing resource from deletion, so it does not block the action.
Why C is wrong: Microsoft Defender for Cloud assesses and improves security posture across resources, which is a governance-adjacent control, but it raises recommendations and alerts rather than preventing a resource from being deleted.
Why D is correct: Correct. A resource lock applies regardless of RBAC permissions, so even an account with the Owner role must first remove the lock before the blocked activity can proceed, which closes the gap that role-based access alone leaves open against accidental deletion.