Examkin

Question

Difficulty: MediumResource Governance: Resource Groups, Tags, and Resource Locks

An administrator manages an Azure subscription that contains a resource group named `rg-network-core`. Inside `rg-network-core`, there is a Virtual Network named `vnet-prod` and a Network Security Group (NSG) named `nsg-prod`. The administrator applies a `CanNotDelete` lock directly to `vnet-prod`, but does not apply any locks to `rg-network-core` or `nsg-prod`.

Evaluate the following statement: The administrator can delete `rg-network-core` without first removing the lock from `vnet-prod`.

Answer: Answer

Answer

False
The statement is false because deleting a resource group requires deleting all resources nested inside it. If any resource inside the group has a CanNotDelete lock, the deletion of the resource group will be blocked.

Step-by-Step Solution

1
Analyze the action being performed and the target resource.
The administrator attempts to delete the resource group `rg-network-core`.
Deleting a resource group recursively deletes all resources contained within that group.
2
Check the locks applied to the resource group and its child resources.
No locks are applied to `rg-network-core`. However, a `CanNotDelete` lock is applied directly to the child resource `vnet-prod`.
We must evaluate if any child resource deletions are blocked by resource locks.
3
Determine the outcome of the deletion request.
The deletion of `rg-network-core` fails because the deletion of its child resource `vnet-prod` is blocked by the active `CanNotDelete` lock.
Azure Resource Manager enforces resource locks at all levels, and a locked child resource blocks the deletion of its parent resource group.

Key Concept

Resource locks prevent deletion of resources, and a lock on a child resource blocks the deletion of the parent resource group.
Estimated Time:1m 0s
Rate this question

Topics

Resource Governance: Resource Groups, Tags, and Resource Locks

More questions from this topic