AZ-305 Question #213: Real Exam Question with Answer & Explanation

Question

Hotspot Question You plan to create an Azure environment that will contain a root management group and 10 child management groups. Each child management group will contain five Azure subscriptions. You plan to have between 10 and 30 resource groups in each subscription. You need to design an Azure governance solution. The solution must meet the following requirements: - Use Azure Blueprints to control governance across all the subscriptions and resource groups. - Ensure that Blueprints-based configurations are consistent across all the subscriptions and resource groups. - Minimize the number of blueprint definitions and assignments. What should you include in the solution? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Answer:

Options

• __typehotspot
• variantdropdown

Explanation

This question tests understanding of Azure Blueprints scope and assignment strategy to maximize consistency while minimizing the number of blueprint definitions and assignments across a large management group hierarchy.

Approach. The correct approach is to create ONE blueprint definition and assign it at the ROOT management group level. By defining the blueprint once and assigning it at the root management group, the blueprint automatically inherits down to all 10 child management groups, all 50 subscriptions (10 groups × 5 subscriptions), and all resource groups within those subscriptions. This satisfies the requirement to minimize blueprint definitions (just 1) and assignments (just 1 assignment at root), while ensuring consistent governance across all subscriptions and resource groups. Blueprints assigned at a management group level are inherited by all child scopes, making root-level assignment the most efficient strategy for enterprise-wide governance.

Concept tested. Azure Blueprints scope inheritance - specifically how blueprint definitions and assignments propagate downward through the management group hierarchy (root → child management groups → subscriptions → resource groups), and how assigning at the highest (root) level minimizes the number of required definitions and assignments while maximizing consistency.

Reference. https://learn.microsoft.com/en-us/azure/governance/blueprints/concepts/lifecycle

No community discussion yet for this question.