hardmulti selectObjective-mapped

A developer has the Contributor role on a resource group and tries to deploy a Windows VM with a public IP address. The deployment fails, even though the role assignment is active. Which two checks should you perform first to confirm why the deployment failed? Select two.

Question 1hardmulti select
Full question →

A developer has the Contributor role on a resource group and tries to deploy a Windows VM with a public IP address. The deployment fails, even though the role assignment is active. Which two checks should you perform first to confirm why the deployment failed? 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

Review Azure Policy assignments at the subscription or management group for deny or modify effects on public IP resources.

Policy can block creation even when RBAC allows the action, so the assignment and effect must be checked first.

B

Best answer

Verify the Contributor role is assigned at the resource group or a higher scope for the target deployment resources.

RBAC scope determines whether the user can create resources in that resource group, so scope validation is essential.

C

Distractor review

Check for a CanNotDelete lock on the resource group because that lock blocks all deployments.

CanNotDelete prevents deletions only; it does not normally block new resource creation or deployment operations.

D

Distractor review

Confirm that the VM size is available in the region because size availability is the most common authorization issue.

SKU availability can fail deployments, but it is unrelated to confirming a permissions-related policy denial.

E

Distractor review

Inspect whether tags are inherited from the subscription because tag inheritance can deny a deployment request.

Tags are useful for organization and cost tracking, but they do not directly deny VM deployments.

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: Review Azure Policy assignments at the subscription or management group for deny or modify effects on public IP resources. — This failure pattern usually means RBAC is permitting the user, but a policy at a higher scope is denying the requested resource type or configuration. The first thing to verify is the policy assignment and its effect, especially if public IP creation is restricted. The second is the RBAC scope, because a Contributor assignment must exist at the resource group or above for the target resources. Together, those checks isolate whether the issue is authorization or policy enforcement. Why others are wrong: A CanNotDelete lock does not block new deployments, only deletions. VM size availability can also cause failures, but it does not confirm a permissions or policy problem. Tags do not deny deployments, so they are not a useful first check here. The scenario is specifically about a deployment failing despite active RBAC, which points to policy versus access scope rather than capacity or metadata concerns.

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.