hardmultiple choiceObjective-mapped

The platform team wants to block deployment of virtual machines that use any size except a small approved list. Operators already have Contributor access and should keep that access for other tasks. Which Azure control should the administrator use to enforce the size restriction?

Question 1hardmultiple choice
Full question →

The platform team wants to block deployment of virtual machines that use any size except a small approved list. Operators already have Contributor access and should keep that access for other tasks. Which Azure control should the administrator use to enforce the size restriction?

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

Assign an Azure Policy with an allowed virtual machine size rule and the Deny effect at the subscription scope.

Azure Policy is designed to enforce configuration rules such as allowed regions or allowed VM sizes. The Deny effect blocks noncompliant deployments even when the user has Contributor permissions, because policy enforcement is separate from RBAC authorization.

B

Distractor review

Create a custom RBAC role that excludes unsupported VM sizes from the Contributor role.

RBAC roles control what actions a user can perform, but they do not evaluate deployment properties such as SKU size. You cannot use RBAC alone to restrict a VM size list.

C

Distractor review

Apply a CanNotDelete lock to the resource group that contains the virtual machines.

A CanNotDelete lock prevents deletion, not deployment of disallowed sizes. It would not stop an administrator from creating a VM with an unsupported SKU.

D

Distractor review

Assign Reader permissions to the operators and rely on Azure portal validation.

Reader removes management rights entirely, which is far beyond the requirement. It also does not represent an enforceable policy-based control for approved VM sizes.

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: Assign an Azure Policy with an allowed virtual machine size rule and the Deny effect at the subscription scope. — This is a policy enforcement requirement, not an authorization requirement. Azure Policy can evaluate the VM size in the deployment request and deny any size outside the approved list, while RBAC permissions remain unchanged for other tasks. That clean separation is exactly why policy is the right tool here. Why others are wrong: RBAC roles cannot inspect the VM SKU being requested, so a custom role cannot enforce allowed sizes. A lock only protects against deletion or writes at a resource boundary and does not validate deployment attributes. Reader is too restrictive and does not solve the actual compliance problem.

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.