An Azure administrator applies a ReadOnly resource lock to a resource group named RG-Web. The resource group contains an Azure App Service plan named ASP-Web. An administrator who is assigned the Owner role at the subscription level attempts to scale up ASP-Web by increasing the instance size. Which of the following describes the outcome of this attempt?
- AThe scaling operation succeeds because the Owner role at the subscription level has permissions that override resource locks.
- The scaling operation fails because the ReadOnly lock is inherited by the App Service plan and prevents configuration updates.Answer
- CThe scaling operation succeeds because a ReadOnly lock only prevents the deletion of resources, not configuration changes.
- DThe scaling operation succeeds because resource locks applied at the resource group level do not inherit to individual resources.
Answer
The scaling operation fails because the ReadOnly lock is inherited by the App Service plan and prevents configuration updates.
The scaling operation fails because the ReadOnly lock is inherited by the App Service plan and prevents configuration updates. Azure resource locks applied at the resource group level are inherited by all resources inside that resource group. A ReadOnly lock restricts all actions that write or modify the resource's configuration, which includes scaling operations. Resource locks apply to all users, meaning even an administrator with Owner permissions is blocked until the lock is removed.
Step-by-Step Solution
Key Concept
Azure resource locks enforce boundaries at subscription, resource group, or resource levels, inheriting down to all child resources. ReadOnly locks block both deletion and modification operations for all users, regardless of RBAC permissions.