mediummulti selectObjective-mapped

An administrator wants to let a help desk group start, stop, and restart virtual machines in one resource group, but the group must not be able to delete the VMs or any other resource in the group. Which two actions should the administrator take? Select two.

Question 1mediummulti select
Full question →

An administrator wants to let a help desk group start, stop, and restart virtual machines in one resource group, but the group must not be able to delete the VMs or any other resource in the group. Which two actions should the administrator 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 custom RBAC role with only VM start, stop, restart, and read actions.

A custom role is required because the built-in roles are broader than the help desk's task. Limiting the actions keeps the permission set aligned with the actual operational need.

B

Best answer

Assign the custom role to the help desk group at the resource group scope.

The resource group scope ensures the help desk can manage only the VMs in that group. Group assignment also keeps future membership changes easy to manage.

C

Distractor review

Assign Virtual Machine Contributor to the help desk group.

Virtual Machine Contributor includes far more capabilities than start, stop, and restart. It would violate the requirement to prevent deletion and other management actions.

D

Distractor review

Apply a CanNotDelete lock to the resource group.

A CanNotDelete lock blocks deletions, but it does not grant the operational permissions needed to start or stop VMs. RBAC is still required.

E

Distractor review

Use Azure Policy to block VM deletion and leave RBAC unchanged.

Policy is not a substitute for the required operational permissions. The group still needs a role assignment that allows the start, stop, and restart actions.

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 with only VM start, stop, restart, and read actions. — The help desk needs a custom RBAC role that includes only the VM read, start, stop, and restart actions, assigned at the resource group scope. This is the cleanest least-privilege design because it grants just the operational tasks the team performs and nothing more. Scope to the resource group keeps the access limited to the intended application boundary. Why others are wrong: Virtual Machine Contributor is too broad for this scenario. A CanNotDelete lock can prevent deletion, but it does not provide the permissions to perform power operations. Azure Policy can help govern configuration, but it does not replace the required RBAC role assignment.

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.