This question requires that you evaluate the underlined text to determine if it is correct. When you need to delegate permissions to several Azure…

In Azure, permissions are managed using Role-Based Access Control (RBAC), which is applied at different scopes. A resource group is a fundamental management scope that acts as a container for related resources. By placing multiple virtual machines into the same resource group, you can assign roles and permissions at the resource group level. These permissions are then inherited by all resources within that group, including all the virtual machines. This provides an efficient way to delegate permissions to several resources simultaneously.

A. No change is needed.

An Azure region is a geographical boundary for resource deployment, not a management scope for assigning RBAC permissions.

B. by using the same Azure Resource Manager template

An ARM template is a tool for declarative deployment and configuration, not a grouping mechanism for ongoing access management.

D. to the same availability zone

An availability zone is a high-availability feature for fault tolerance within a region and is not a scope for RBAC assignments.

---

1. Microsoft Learn. "What is Azure role-based access control (Azure RBAC)?". Under the section "Scope," it is stated: "You can specify a scope at four levels: management group, subscription, resource group, and resource. Scopes are structured in a parent-child relationship. When you grant access at a parent scope, those permissions are inherited by the child scopes." This confirms that a resource group is a primary scope for applying permissions that are inherited by the resources within it.

2. Microsoft Learn. "Azure Resource Manager overview". Under the section "Resource groups," it explains: "A resource group is a container that holds related resources for an Azure solution... you can manage all the resources for your solution as a group." This highlights the role of resource groups in collective management, which includes access control.

3. Microsoft Learn. "Regions and Availability Zones in Azure". This document defines regions and availability zones in the context of geography, latency, and resiliency. It does not identify them as scopes for applying permissions, which supports the exclusion of options A and D.