The answer is Tags. Tags are metadata key-value pairs applied to Azure resources and resource groups, and they persist even when resources are moved between resource groups, making them the correct feature for maintaining ownership and chargeback tracking visibility. Unlike resource locks or policies, tags are specifically designed for cost tracking, ownership attribution, and resource categorization, ensuring that billing and accountability data follows the resource regardless of its location. On the AZ-104 exam, this question tests your understanding of how tags differ from other management features—a common trap is confusing tags with resource groups or naming conventions, but remember that tags are the only option that stays attached during moves. For a quick memory tip: think of tags as sticky labels that travel with the resource, while resource groups are just containers that can change.
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
Cost reporting extract
Resource name: vm-fin-01 | Resource group: rg-west-prod | Department: blank | Environment: Prod
Resource name: sql-fin-01 | Resource group: rg-west-data | Department: blank | Environment: Prod
Resource name: app-fin-01 | Resource group: rg-east-app | Department: blank | Environment: Test
Requirement: Finance wants each resource to retain ownership metadata for reporting and chargeback, regardless of which resource group the resource is placed in later.
Based on the exhibit, which Azure feature should the administrator add so ownership and chargeback information remains visible even if resources are moved between resource groups?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Tags
Tags are metadata key-value pairs that can be assigned to Azure resources and resource groups. They persist even when resources are moved between resource groups, making them ideal for tracking ownership and chargeback information across organizational boundaries. Unlike other options, tags are specifically designed for cost tracking, ownership attribution, and resource categorization.
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.
✗
Management groups
Why it's wrong here
Management groups organize subscriptions; they do not store per-resource ownership metadata such as department or environment.
✓
Tags
Why this is correct
Tags are designed to attach flexible metadata directly to resources, and the values remain useful for filtering and chargeback reporting.
Related concept
Read the scenario before looking for a memorised answer.
✗
Resource locks
Why it's wrong here
Locks protect resources from changes or deletion, but they do not provide ownership or cost-allocation metadata.
✗
Role assignments
Why it's wrong here
Role assignments define permissions for identities, not business metadata for reporting or chargeback.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Resource locks (which prevent deletion) with metadata persistence, or assume Role assignments follow resources across moves, when in fact RBAC assignments are scoped to the original resource group and are lost upon relocation.
Detailed technical explanation
How to think about this question
Under the hood, Azure Tags are stored as part of the resource's ARM metadata in the Azure Resource Manager, independent of the resource group container. When a resource is moved, the tags are preserved because they are properties of the resource itself, not the resource group. In real-world scenarios, organizations use tags like 'CostCenter', 'Owner', or 'Environment' to feed into Azure Cost Management and billing exports, enabling accurate chargeback even after resource reorganization.
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: Tags — Tags are metadata key-value pairs that can be assigned to Azure resources and resource groups. They persist even when resources are moved between resource groups, making them ideal for tracking ownership and chargeback information across organizational boundaries. Unlike other options, tags are specifically designed for cost tracking, ownership attribution, and resource categorization.
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 →
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.