How to Associate Each VM with Its Department in RG1
Your company has serval departments. Each department has a number of virtual machines (VMs). The company has an Azure subscription that contains a resource group named RG1. All VMs are located in RG1. You want to associate each VM with its respective department. What should you do?
Community Insight
This question tests whether you recognize tags as the lightweight metadata mechanism for logically categorizing resources inside one resource group; the trap is reaching for a structural change like creating resource groups or management groups when none is needed.
When all departmental VMs already live in a single Azure resource group (RG1) and you only need a logical department association, Azure resource tags are the intended mechanism. The question tests knowledge of when tags—not resource groups, management groups, or VM settings—are the correct organizational tool, making C the right answer.
Option B (create a resource group per department) is the most tempting distractor, because resource groups feel like an 'organization' feature—but the scenario fixes all VMs in RG1 and asks only for an association, not a restructure. Option A fails because management groups govern subscriptions, not resources within a single subscription.
Community Discussion (124 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Azure tags are name/value pairs (for example, Department=HR or Department=Finance) applied to resources purely as metadata for logical organization, cost allocation, ownership, and reporting. Because the question states all VMs already sit in RG1 and only asks to "associate each VM with its respective department," no structural change is required—tags satisfy this directly. Tags work across resource types and can be applied per resource in the portal, CLI, or ARM/Bicep, and they support filtering and chargeback scenarios mentioned by green_arrow. As pb7o61 explained, tags let you categorize and organize resources "based on your organization's needs" without moving anything.Exam Strategy
On AZ-104, when a question asks to organize, categorize, track costs, or identify ownership of resources that must stay where they are, default to tags. Only choose resource groups or management groups when the question explicitly mentions moving resources, applying policy, or governing multiple subscriptions.
Frequently Asked Questions
Why can't I create a resource group per department to associate the VMs?
The scenario states all VMs are already in RG1; creating new resource groups would require moving them, which goes beyond the requested logical association and changes the existing structure.
Why are Azure management groups incorrect for department association?
Management groups govern subscriptions hierarchically (policies, RBAC, compliance). This environment has one subscription and asks only about organizing resources inside RG1, so they don't apply.
Related Analysis
Practice All AZ-104 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-104 Practice Test →