The finance team wants every resource created in one resource group to carry the same CostCenter tag automatically. They want to reduce manual entry and keep the tag value consistent. What should you configure?

Ask users to add the tag manually to every resource

Manual tagging is prone to mistakes and does not enforce a consistent value.

Assign a Reader role to the finance team

Reader controls access, not tag creation or tag inheritance behavior.

Apply a CanNotDelete lock to the resource group

A lock helps protect resources from deletion, but it does not create or copy tags.

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: Use Azure Policy to inherit the CostCenter tag from the resource group — Azure Policy is the right tool when you want to standardize tags automatically across deployed resources. Using a tag inheritance policy lets Azure copy the CostCenter value from the resource group to child resources, reducing human error and making chargeback reporting easier. This is better than relying on manual tagging because it enforces consistency at deployment time. Why others are wrong: Manual tagging depends on people remembering to do the right thing every time. Reader is unrelated because access permissions do not apply tags. A lock protects against deletion, not metadata consistency. The goal is automated tag propagation, which is a policy-based governance task.

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.