nerdexam
Microsoft

AZ-500 · Question #229

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…

The correct answer is A. Yes. Option A (Yes) is correct because creating an initiative allows you to group multiple policy definitions together as a single unit, and scoping the assignment to the Tenant Root Group management group ensures the policies are automatically inherited by all subscriptions beneath…

Submitted by packet_pusher· Mar 6, 2026Secure Azure using Microsoft Defender for Cloud and Microsoft Sentinel

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You use Azure Security Center for the centralized policy management of three Azure subscriptions. You use several policy definitions to manage the security of the subscriptions. You need to deploy the policy definitions as a group to all three subscriptions. Solution: You create an initiative and an assignment that is scoped to the Tenant Root Group management group. Does this meet the goal?

Options

  • AYes
  • BNo

How the community answered

(25 responses)
  • A
    80% (20)
  • B
    20% (5)

Explanation

Option A (Yes) is correct because creating an initiative allows you to group multiple policy definitions together as a single unit, and scoping the assignment to the Tenant Root Group management group ensures the policies are automatically inherited by all subscriptions beneath it - including all three in this scenario. This is the most efficient and scalable approach, as any subscription within the tenant falls under the Tenant Root Group hierarchy.

Why the distractor (No) is wrong: There is no incorrect option to refute here beyond the implied alternative approaches. Assigning policies individually to each subscription, or using a management group that doesn't encompass all three subscriptions, would fail to meet the goal of deploying to all three subscriptions simultaneously in a single action.

Key concept: An initiative = a collection of policy definitions; an assignment = where it applies. The Tenant Root Group sits at the very top of the Azure management hierarchy, meaning everything beneath it (all management groups, subscriptions, and resource groups) inherits assigned policies.

Memory Tip: Think of the Tenant Root Group as the "CEO" of your Azure hierarchy - policies assigned there cascade down to everyone. Remember: Initiative = Bundle, Tenant Root = Top of the Tree.

Topics

#Azure Policy#Management Groups#Policy Initiatives#Policy Assignment

Community Discussion

No community discussion yet for this question.

Full AZ-500 Practice