mediummultiple choiceObjective-mapped

Exhibit

Current assignments for RG-App:
- HelpDeskGroup -> Reader
- PlatformAdmins -> Contributor
Business requirement:
- HelpDeskGroup can start, stop, and restart VMs only
- HelpDeskGroup must not manage NICs, disks, or other resources

Based on the exhibit, the help desk team must be able to restart virtual machines in RG-App, but they must not be able to create, delete, or resize VMs. What is the best action?

Question 1mediummultiple choice
Full question →

Based on the exhibit, the help desk team must be able to restart virtual machines in RG-App, but they must not be able to create, delete, or resize VMs. What is the best action?

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

Distractor review

Assign Virtual Machine Contributor to HelpDeskGroup at the subscription scope.

This grants far more than restart capability and at the subscription scope it applies to more resources than needed, which violates least privilege.

B

Distractor review

Assign Contributor to HelpDeskGroup at RG-App.

Contributor is too broad because it allows many resource management actions beyond restarting VMs, including creating and deleting resources in the resource group.

C

Best answer

Create a custom RBAC role that allows VM start, restart, and deallocate actions, then assign it at RG-App.

A custom role is the best fit when no built-in role is narrow enough. Assigning it at the resource group scope limits the permission to RG-App, while the role itself can be restricted to only the VM operational actions that the help desk needs.

D

Distractor review

Assign Owner to HelpDeskGroup at RG-App and use Azure Policy to block unwanted changes.

Owner is even more permissive than Contributor, and Azure Policy does not replace authorization. Policy can enforce compliance, but it does not narrow RBAC permissions for the team.

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 custom RBAC role that allows VM start, restart, and deallocate actions, then assign it at RG-App. — A custom RBAC role assigned at RG-App is the best choice because the requirement is narrower than any common built-in role. The role can include only the VM operational actions needed for start, stop, restart, or deallocate, while excluding create, delete, resize, and non-VM permissions. Scoping the assignment to the resource group keeps the access limited to the intended workload. Why others are wrong: Virtual Machine Contributor and Contributor both grant broader management rights than required, which increases risk. Owner is the broadest option and is inappropriate for a help desk function. Azure Policy cannot reduce the authorization surface of RBAC; it only governs compliance behavior.

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.