mediummultiple choiceObjective-mapped

Exhibit

Resource group requirement:
- Scope: RG-Finance
- Every new resource must carry CostCenter=FIN
- Missing tag should be added automatically when possible
- Deployments must not be blocked
Current state:
- Teams manually add tags today
- Inconsistent tag values are common

Based on the exhibit, every resource created in RG-Finance must automatically receive CostCenter=FIN, but deployments should not fail if the tag is omitted. What should you configure?

Question 1mediummultiple choice
Full question →

Based on the exhibit, every resource created in RG-Finance must automatically receive CostCenter=FIN, but deployments should not fail if the tag is omitted. What should you configure?

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 the Modify effect at RG-Finance.

Modify is the right policy effect when you want Azure to add or update a tag without failing the deployment. Assigning it at the resource group ensures the requirement applies only to RG-Finance and keeps the CostCenter value consistent.

B

Distractor review

Assign an RBAC role that forces all users to enter the tag.

RBAC cannot force tag values in the deployment payload. It only controls whether the user is authorized to create or manage resources.

C

Distractor review

Apply a ReadOnly lock to the resource group.

A ReadOnly lock blocks changes and would prevent normal resource creation or updates. It does not help with automated tagging.

D

Distractor review

Use Azure Policy with a Deny effect at the management group.

Deny would block deployments that miss the tag, which conflicts with the requirement that deployments should not fail. The scope is also broader than necessary.

Common exam trap

Common exam trap: ACLs stop at the first match

ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.

Technical deep dive

How to think about this question

ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.

KKey Concepts to Remember

  • Standard ACLs match source addresses.
  • Extended ACLs can match source, destination, protocol and ports.
  • The first matching ACL entry is used.
  • There is usually an implicit deny at the end.

TExam Day Tips

  • Check inbound versus outbound direction.
  • Read the ACL from top to bottom.
  • Look for a broader permit or deny above the intended line.

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?

Standard ACLs match source addresses.

What is the correct answer to this question?

The correct answer is: Assign an Azure Policy with the Modify effect at RG-Finance. — Modify is the best effect because it can automatically add the CostCenter tag without interrupting deployments. That matches the requirement to reduce manual tagging while avoiding deployment failures. Assigning the policy at RG-Finance keeps the control focused on the one resource group that needs consistent cost tracking and avoids unnecessary impact elsewhere. Why others are wrong: RBAC does not validate or inject tag values. ReadOnly blocks writes and would interfere with resource creation. Deny enforces compliance by failing noncompliant deployments, which is explicitly not what this scenario asks for.

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.