AZ-104 Manage Azure Identities and Governance Practice Question
A department wants three related policies grouped together and assigned as one unit to a set of subscriptions. Which two statements about an Azure Policy initiative are correct? Select two.
⚠ Common exam trap
Candidates often confuse Azure Policy initiatives with RBAC roles or resource locks, mistakenly thinking initiatives manage permissions or protect resources, when in fact they only enforce compliance rules.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
An initiative groups multiple policy definitions into one assignment.
Option A is correct because an Azure Policy initiative (also called a policy set) is specifically designed to bundle multiple related policy definitions together so they can be managed and assigned as a single unit, which matches the department's goal of grouping three related policies. Option B is correct because initiatives, like individual policies, can be assigned at management group scope, and assignments at that scope are inherited by all child subscriptions, which satisfies the requirement to apply the grouped policies to a set of subscriptions. Option C is incorrect because granting Azure permissions is the role of Azure RBAC role assignments, not Azure Policy initiatives. Option D is incorrect because resource locks are a separate Azure feature managed via Microsoft.Authorization/locks, and initiatives do not replace them. Option E is incorrect because creating resource groups is done through the Azure portal, CLI, PowerShell, ARM/Bicep templates, or Terraform, not through a policy initiative.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
An initiative groups multiple policy definitions into one assignment.
Why this is correct
An initiative bundles several policy definitions into a single assignable unit, so the department's three related policies are grouped and applied together rather than assigned individually. This directly satisfies the requirement to manage them as one unit across the target subscriptions.
- ✓
An initiative can be assigned at management group scope to cover child subscriptions.
Why this is correct
Assigning the initiative at management group scope lets it inherit down to every child subscription beneath that group, covering the department's subscriptions in one assignment. This satisfies the constraint of applying the grouped policies to a set of subscriptions without per-subscription assignments.
- ✗
An initiative grants Azure permissions to users.
Why it's wrong here
Initiatives evaluate resource compliance against policy rules; granting Azure permissions is the function of Microsoft Entra ID role assignments or Azure RBAC, not policy. It is tempting because both are assigned at management-group or subscription scope, but an initiative is correct when you need several related policy definitions applied as one unit.
When this WOULD be correct
If the question were about Azure RBAC, such as 'Which feature grants Azure permissions to users?', then 'role assignment' would be correct. But 'initiative' is never correct for granting permissions.
- ✗
An initiative replaces resource group locks.
Why it's wrong here
Locks and initiatives operate on entirely separate planes: resource locks prevent modification or deletion of resources, while an initiative merely bundles policy definitions for assignment. It is tempting because both are governance controls applied at scale, but an initiative would be the right choice when you need to assign several related policies as a single unit.
When this WOULD be correct
In a question asking 'Which Azure feature prevents accidental deletion of a resource group?', 'Resource group lock' would be the correct answer. The scenario would involve protecting critical resources from deletion or modification.
- ✗
An initiative is used to create a new resource group.
Why it's wrong here
Initiatives contain policy definitions only; they cannot provision resources such as resource groups, which requires deployment tooling like ARM templates or Bicep. It is tempting because initiatives are assigned to scopes including subscriptions, but the correct use is grouping related policy definitions for one assignment, not creating infrastructure.
When this WOULD be correct
If the question were 'Which Azure feature can be used to enforce naming conventions on new resource groups?', then an initiative containing a policy that requires specific naming patterns would be correct, as initiatives can include policies that evaluate resource creation.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓An initiative groups multiple policy definitions into one assignment.Correct answer▾
Why this is correct
An initiative bundles several policy definitions into a single assignable unit, so the department's three related policies are grouped and applied together rather than assigned individually. This directly satisfies the requirement to manage them as one unit across the target subscriptions.
✗An initiative grants Azure permissions to users.Wrong answer — click to see why▾
Why this is wrong here
An initiative does not grant permissions; Azure RBAC roles are used for granting permissions. Initiatives are for grouping and assigning policy definitions, not for access control.
★ When this WOULD be the correct answer
If the question were about Azure RBAC, such as 'Which feature grants Azure permissions to users?', then 'role assignment' would be correct. But 'initiative' is never correct for granting permissions.
Why candidates choose this
Candidates may confuse 'initiative' with 'role' or think that assigning a policy initiative somehow grants permissions because it can enforce compliance, but permissions are separate from policies.
✗An initiative replaces resource group locks.Wrong answer — click to see why▾
Why this is wrong here
An initiative does not replace resource group locks; it groups policy definitions for assignment. Resource group locks are a separate Azure governance feature that prevents accidental deletion or modification.
★ When this WOULD be the correct answer
In a question asking 'Which Azure feature prevents accidental deletion of a resource group?', 'Resource group lock' would be the correct answer. The scenario would involve protecting critical resources from deletion or modification.
Why candidates choose this
Candidates may confuse policy initiatives with other governance tools like locks, assuming initiatives can enforce deletion protection, but they are designed for policy compliance, not resource locking.
✗An initiative is used to create a new resource group.Wrong answer — click to see why▾
Why this is wrong here
An initiative is a group of policy definitions, not a tool for creating resource groups. Resource groups are created via Azure Resource Manager templates, CLI, or portal, not through policy initiatives.
★ When this WOULD be the correct answer
If the question were 'Which Azure feature can be used to enforce naming conventions on new resource groups?', then an initiative containing a policy that requires specific naming patterns would be correct, as initiatives can include policies that evaluate resource creation.
Why candidates choose this
Candidates may confuse the purpose of initiatives with that of Azure Blueprints or ARM templates, which can create resource groups. The word 'initiative' sounds like an active action, leading to the misconception that it can create resources.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
Learn chapter
Azure Update Management Center
Key term
Azure Policy
Azure Policy is a service in Microsoft Azure that lets you create, assign, and manage rules to ensure your resources stay compliant with your company standards and service-level agreements.
Key term
Management group
A Management group is a container in Microsoft Azure that helps you organize and manage access, policies, and compliance across multiple Azure subscriptions.
About these practice questions
This AZ-104 question is part of Courseiva's 1,053-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.