hardmultiple choiceObjective-mapped

A finance team wants every resource created in one production resource group to carry CostCenter=PRD automatically. They do not want deployments blocked if a team forgets the tag, but they do want existing resources and future resources in that resource group to converge on the correct tag value. What should the administrator configure?

Question 1hardmultiple choice
Full question →

A finance team wants every resource created in one production resource group to carry CostCenter=PRD automatically. They do not want deployments blocked if a team forgets the tag, but they do want existing resources and future resources in that resource group to converge on the correct tag value. What should the administrator 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

Distractor review

Apply a CanNotDelete lock to the production resource group.

A lock can protect resources from deletion, but it does not add or correct tags. It does not meet the cost-tracking requirement.

B

Best answer

Assign a modify policy for CostCenter=PRD at the production resource group scope and create a remediation task.

A modify policy can add or correct the tag without blocking deployment, which matches the business requirement. Assigning it at the resource-group scope limits the effect to only that production workload, and remediation updates existing resources so both old and new items converge on the same tag value.

C

Distractor review

Assign Contributor on the subscription and require teams to enter the tag manually.

Contributor only grants permissions; it does not enforce consistent tagging. Manual entry also creates drift and depends on user discipline, which the business specifically wants to avoid.

D

Distractor review

Set the tag on the management group and expect all resources to inherit it automatically.

Management groups do not natively behave like tag templates for resources. A tag set there will not automatically flow to every resource in the way this requirement needs.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

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?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Assign a modify policy for CostCenter=PRD at the production resource group scope and create a remediation task. — Because the team wants nonblocking enforcement plus correction of existing drift, a modify policy is the right tool. Scope it to the specific resource group so it targets only the production workload, then run remediation so current resources are brought into compliance. This satisfies cost tracking without interrupting deployments. Why others are wrong: A CanNotDelete lock does not manage tags. Contributor plus manual entry is operationally weak and does not guarantee consistency. Management groups are not a tag inheritance mechanism for resources, so that approach would not reliably set the required CostCenter value.

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.