Microsoft 365 Certified Endpoint Administrator (MD-102) Practice Test

What is the correct order of steps to implement role-based access control (RBAC) in Azure?

1. Create a resource group > Create a custom role > Define the scope of the role > Assign the role to a user or group

2. Define the scope of the role > Create a resource group > Create a custom role > Assign the role to a user or group

3. Create a custom role > Assign the role to a user or group > Define the scope of the role > Create a resource group

4. Assign the role to a user or group > Create a resource group > Create a custom role > Define the scope of the role

The correct answer is: Create a resource group > Create a custom role > Define the scope of the role > Assign the role to a user or group

The process of implementing role-based access control (RBAC) in Azure starts with creating a resource group, which serves as a logical container for Azure resources. This step is essential because all subsequent configurations, such as defining roles and scopes, will be tied to the specific resources within that group. After establishing the resource group, the next step is to create a custom role. Custom roles allow you to define specific permissions tailored to the needs of your organization or project. Creating a role before defining its scope helps ensure that the role encompasses the permissions that will be applied in that scope. Once the custom role is created, you define the scope of that role, which can either be at the subscription level, resource group level, or the level of an individual resource. Defining the scope specifies where the permissions associated with the role will apply. Finally, the last step involves assigning the role to a user or group. This assignment ensures that the designated user or group has the appropriate permissions to access and manage the resources within the defined scope. This sequence of steps ensures that the access control is methodical, focusing on specific resources and their corresponding permissions, effectively granting the necessary access to individuals or teams while maintaining security protocols within Azure.