An enterprise is scaling its Azure footprint and needs to grant a newly formed team of developers permission to restart virtual machines in a development resource group. To ensure scalable management and adhere to the principle of least privilege, how should you assign the required permissions?
- AAssign the Virtual Machine Contributor role directly to each developer's user account at the resource group scope.
- Create a Microsoft Entra ID security group containing the developers, and assign the Virtual Machine Contributor role to the group at the resource group scope.Answer
- CConfigure a Privileged Identity Management (PIM) role assignment that makes the Virtual Machine Contributor role permanently active for each individual developer.
- DAssign an Azure Policy with a Deny effect to the resource group to prevent other users from managing the virtual machines, rather than using RBAC roles.
Answer
Create a Microsoft Entra ID security group containing the developers, and assign the Virtual Machine Contributor role to the group at the resource group scope.
The correct option outlines the standard best practice for Azure RBAC governance. Permissions should be granted to a group rather than individuals to ease maintenance. In addition, the assignment is restricted to the specific resource group to enforce the principle of least privilege.
Step-by-Step Solution
Key Concept
Azure RBAC Group Assignment and Least Privilege Scope
Estimated Time:45s