Question 213 — Domain 2-Describe Azure architecture and services | AZ-900 Practice Exam | 399 Questions
Arrange the following Azure portal steps for adding a role assignment to a resource in the correct order.
Instruction: Drag and drop the items into the correct order, starting with the first step at the top.
- Select the user, group, service principal, or managed identity
- Review the role assignment
- Open Access control (IAM)
- Select the role to assign
- Submit the role assignment
- Select Add role assignment
- Open the target Azure resource
Correct answers
- Open the target Azure resource
- Open Access control (IAM)
- Select Add role assignment
- Select the role to assign
- Select the user, group, service principal, or managed identity
- Review the role assignment
- Submit the role assignment
Explanations
Correct order
Open the target Azure resource
Open Access control (IAM)
Select Add role assignment
Select the role to assign
Select the user, group, service principal, or managed identity
Review the role assignment
Submit the role assignment
The role assignment flow in the Azure portal follows a rigid sequence that cannot be altered. You begin by opening the specific Azure resource to which access will be granted; the IAM blade is context‑sensitive and only accessible from within the resource’s menu. Opening Access control (IAM) reveals the existing permissions and the option to add a new assignment. Selecting Add role assignment launches the dedicated configuration form, where the first mandatory step is to choose the role itself (e.g., Contributor, Reader) because the role defines what actions are allowed. Only after the role is selected does the portal present the field to select the assignee—a user, group, service principal, or managed identity—since the assignment ties a principal to that role. With both role and principal specified, you proceed to review the role assignment to verify all details are correct; the portal will not allow submission until this review step is completed. Finally, submitting the assignment persists the configuration. Every step depends on the completion of the previous one, and no step can be skipped or reordered regardless of tenant, user permissions, or resource type.