Question 80
A delegated security administrator should create and remove Azure RBAC role assignments for resources in one existing resource group, but must not modify those resources. Which role and scope best satisfy that assignment?
Explanation
Correct Answer
Role Based Access Control Administrator is designed for managing Azure role assignments without handing out general resource Contributor permissions. Assigning it at the relevant resource group delegates access-administration authority over that scope and its descendants, not over the whole subscription. Built-in role-assignment permissions remain subject to applicable conditions and deny assignments, so the organization should inspect the effective access and enforce any additional restrictions required by its policy.
Incorrect Answers
Reader allows inspection of configuration and existing role assignments where permitted, but not creation or deletion of those grants. It also expands visibility beyond the one resource group that the delegate owns. The case requires the write and delete actions on Azure role assignments, which are provided by an access-administration role rather than read-only access.
Owner can manage role assignments, but also grants extensive resource-management privileges throughout the subscription. The user expressly must not modify resources and needs authority only in one resource group. Giving subscription Owner would violate both the permissions and scope restrictions; the narrower specialized RBAC Administrator assignment is the appropriate delegation.
Contributor generally manages Azure resources but excludes the permission to create or remove Azure RBAC role assignments. That makes it both too broad for unrelated resource modifications and insufficient for this specific access-administration task. The dedicated RBAC Administrator role provides the relevant assignment operations without turning the delegate into an infrastructure operator.