easymulti selectObjective-mapped

A project team adds and removes contractors every month. The admin wants Azure access to update automatically when membership changes without editing role assignments for each person. Which two actions should the admin take? Select two.

Question 1easymulti select
Full question →

A project team adds and removes contractors every month. The admin wants Azure access to update automatically when membership changes without editing role assignments for each person. Which two actions should the admin take? Select two.

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Create a Microsoft Entra ID security group for the contractors.

A security group gives the administrator one place to manage a changing set of users. When contractors join or leave, membership can be updated without rewriting Azure role assignments. This is the standard way to delegate access for a team or project that changes often.

B

Distractor review

Assign the Azure RBAC role directly to each contractor user account.

Direct user assignments work, but they require repeated updates every time a contractor changes. That creates extra administration and increases the chance of missing someone during a transition.

C

Best answer

Assign the Azure RBAC role to the security group.

Assigning the role to the group keeps the permission model simple and scalable. The role stays in place while membership changes, so access automatically follows the users who are added to the group.

D

Distractor review

Create a management group for the contractors.

Management groups organize subscriptions, not individual contractor access. They are useful for governance at a higher level, but they do not solve day-to-day user membership management.

E

Distractor review

Use a resource lock to control access.

Resource locks protect resources from deletion or modification, but they do not grant or delegate access. Locks are a protection feature, not an identity or authorization feature.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Related practice questions

Related AZ-104 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Create a Microsoft Entra ID security group for the contractors. — A security group plus a role assignment to that group is the simplest way to manage access for a changing contractor team. The administrator can add or remove people from the group without touching the Azure RBAC assignment itself. This reduces manual work, keeps permissions consistent, and supports least-privilege administration because the same role can be controlled through membership rather than individual user assignments. Why others are wrong: Assigning roles directly to each contractor is harder to maintain and does not scale well. A management group is for organizing subscriptions and governance, not for tracking people. Resource locks are unrelated to permissions and cannot be used to grant access. The goal is to centralize authorization around a group so membership changes automatically affect access.

What should I do if I get this AZ-104 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.