The answer is the Modify effect. This is correct because Modify uses a merge operation to add the CostCenter=042 tag to new resources during deployment, and its conflictEffect can be set to audit, which allows the deployment to succeed even if the tag is missing—unlike Deny, which would block the resource, or Append, which is deprecated and only applies to non-tag properties. On the AZ-104 exam, this scenario tests your understanding of policy effects for tag governance without disrupting deployments; a common trap is choosing Append, which cannot add tags, or Deny, which causes failure. Remember the mnemonic: “Modify merges, Append can’t tag, Deny denies—Modify audits to avoid the cries.”
AZ-104 Manage Azure Identities and Governance Practice Question
This AZ-104 practice question tests your understanding of manage azure identities and governance. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Policy design notes:
- Scope: subscription
- Target: all resource groups
- Desired outcome: add tag CostCenter=042 automatically
- Requirement: do not block the deployment if the tag is omitted
Policy effects being considered:
- Deny
- Audit
- Append
- Modify
Based on the exhibit, a subscription policy must add CostCenter=042 to new resources, and deployments must not fail if the tag is missing. Which policy effect should you use?
Policy design notes:
- Scope: subscription
- Target: all resource groups
- Desired outcome: add tag CostCenter=042 automatically
- Requirement: do not block the deployment if the tag is omitted
Policy effects being considered:
- Deny
- Audit
- Append
- Modify
A
Deny
Why wrong: Deny would block the deployment instead of allowing it to continue when the tag is missing.
B
Audit
Why wrong: Audit only records non-compliance and does not automatically add the missing tag.
C
Append
Why wrong: Append can add properties in some request scenarios, but it is not the best choice for automatic tag correction behavior.
D
Modify
Modify is used to automatically change resource requests, such as adding or correcting tags, without blocking deployment.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Modify
The 'Modify' effect (option D) is correct because it can add the CostCenter=042 tag to new resources without causing deployment failures if the tag is missing. Unlike 'Deny', which blocks non-compliant resources, or 'Append', which is deprecated and only works on non-tag properties, 'Modify' uses a 'merge' operation to add tags during resource creation or update, and its 'conflictEffect' can be set to 'audit' to ensure deployments succeed even when the tag is absent.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Deny
Why it's wrong here
Deny would block the deployment instead of allowing it to continue when the tag is missing.
✗
Audit
Why it's wrong here
Audit only records non-compliance and does not automatically add the missing tag.
✗
Append
Why it's wrong here
Append can add properties in some request scenarios, but it is not the best choice for automatic tag correction behavior.
✓
Modify
Why this is correct
Modify is used to automatically change resource requests, such as adding or correcting tags, without blocking deployment.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse 'Append' with 'Modify' because both can alter resources, but 'Append' is deprecated and cannot handle tags, while 'Modify' is the modern effect designed specifically for tag operations with flexible conflict resolution.
Trap categories for this question
Scenario analysis trap
Append can add properties in some request scenarios, but it is not the best choice for automatic tag correction behavior.
Detailed technical explanation
How to think about this question
Under the hood, the 'Modify' effect in Azure Policy uses a 'merge' operation to add or update tags on resources during creation or update, and its 'conflictEffect' property (set to 'audit' or 'deny') controls behavior when a tag already exists. For this requirement, setting 'conflictEffect' to 'audit' ensures the policy adds the tag if missing but does not block the deployment if the tag is already present with a different value—it simply logs a non-compliance entry. This is critical in real-world scenarios where teams need to enforce tagging standards without breaking CI/CD pipelines or automated deployments.
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.
TExam Day Tips
→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.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Manage Azure Identities and Governance — This question tests Manage Azure Identities and Governance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Modify — The 'Modify' effect (option D) is correct because it can add the CostCenter=042 tag to new resources without causing deployment failures if the tag is missing. Unlike 'Deny', which blocks non-compliant resources, or 'Append', which is deprecated and only works on non-tag properties, 'Modify' uses a 'merge' operation to add tags during resource creation or update, and its 'conflictEffect' can be set to 'audit' to ensure deployments succeed even when the tag is absent.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. RG-Prod hosts line-of-business workloads. The business wants to prevent accidental deletion of the resource group during change freezes and also ensure every new resource carries a CostCenter tag for chargeback. Which two governance controls should be used? Select two.
hard
✓ A.Apply a CanNotDelete lock to RG-Prod.
B.Apply a ReadOnly lock to RG-Prod.
✓ C.Use Azure Policy with a Modify effect to add the CostCenter tag to new resources.
D.Grant Reader to the finance team on the resource group.
E.Create a private endpoint for RG-Prod.
Why A: Option A is correct because applying a CanNotDelete lock to RG-Prod prevents the resource group from being deleted during change freezes, which directly meets the requirement to prevent accidental deletion. This lock type allows read and update operations but blocks delete operations, making it ideal for protecting critical resources without impacting ongoing workloads.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.