An organization is setting up an Azure environment and needs to delegate resource management for a development team. A deployment specialist must be able to create, modify, and delete virtual machines within a specific resource group named ProjectX-RG. However, the specialist must not be allowed to delegate access permissions to other users or manage resource locks on ProjectX-RG. Which of the following options should you configure to meet these requirements?
- Assign the Contributor role to the specialist at the resource group scopeCevap
- BAssign the Owner role to the specialist at the resource group scope
- CAssign an Azure Policy definition to the resource group that allows virtual machine creation
- DApply a ReadOnly resource lock to the ProjectX-RG resource group
Cevap
Assign the Contributor role to the specialist at the resource group scope
Assigning the Contributor role at the resource group scope allows the specialist to create and manage virtual machines within the specified resource group. The Contributor role does not grant permissions to manage access controls (which requires Owner or User Access Administrator) or change resource locks, satisfying all constraints.
Adım Adım Çözüm
Anahtar Kavram
Azure Role-Based Access Control (RBAC) manages access by assigning roles (like Owner and Contributor) at specific scopes, while Azure Policy enforces compliance and Resource Locks prevent accidental changes.