An administrator is configuring access control and compliance for an Azure resource group named 'Dev-RG'. A team of developers must be able to create, delete, and modify virtual machines within 'Dev-RG', but they must not be able to delegate access permissions to other users. Additionally, the organization wants to ensure that all virtual machines in 'Dev-RG' are deployed only in the East US region.
Which configuration should the administrator use to meet these requirements?
- Assign the Contributor role to the developers at the 'Dev-RG' scope, and assign an Azure Policy definition to 'Dev-RG'.Answer
- BAssign the Contributor role to the developers at the 'Dev-RG' scope, and configure a custom Azure role-based access control (RBAC) role to enforce the allowed regions.
- CAssign the Owner role to the developers at the 'Dev-RG' scope, and assign an Azure Policy definition to 'Dev-RG'.
- DAssign the Contributor role to the developers at the 'Dev-RG' scope, and apply a ReadOnly resource lock to 'Dev-RG'.
Answer
Assign the Contributor role to the developers at the 'Dev-RG' scope, and assign an Azure Policy definition to 'Dev-RG'.
The combination of assigning the Contributor role at the resource group scope and applying an Azure Policy definition correctly satisfies the requirements. The Contributor role grants full access to manage resources within the resource group but does not allow assigning roles to other users. Azure Policy is designed to enforce resource compliance rules, such as restricting deployments to a specific region.
Step-by-Step Solution
Key Concept
Azure Role-Based Access Control (RBAC) manages access permissions, while Azure Policy enforces resource property compliance.