Hotspot Question You have the hierarchy of Azure resources shown in the following exhibit. You create the Azure Blueprints definitions shown in the following table. To which objects can you assign…

Question

Exhibit

Answer Area

• Blueprint1:
  ManagementGroup1 onlyManagementGroup1, Subscription1, and RG1 onlyManagementGroup1, Subscription1, RG1, and VM1Subscription1 onlyTenant Root Group onlyTenant Root Group, ManagementGroup1, and Subscription1 only
• Blueprint2:
  ManagementGroup1 onlySubscription1 and RG1 onlySubscription1 onlySubscription1, RG1, and VM1

Explanation

This question tests understanding of Azure Blueprints scope and assignment rules - specifically, a Blueprint definition can only be assigned to the management group where it was defined or to any child subscriptions/management groups beneath it.

Approach. A Blueprint definition is saved (defined) at a specific management group scope. It can then be assigned to that same management group OR to any subscription or management group that is a descendant (child) of that management group. Blueprint1, defined at a higher-level management group, can be assigned to that management group and all child management groups and subscriptions beneath it. Blueprint2, defined at a lower-level management group or subscription scope, can only be assigned to that scope and its children - it cannot be assigned to parent management groups or sibling subscriptions outside its hierarchy branch. Therefore, Blueprint1 has broader assignment eligibility while Blueprint2 is restricted to its defined scope and below.

Concept tested. Azure Blueprints definition scope and assignment scope - a blueprint can only be assigned at or below the management group where it was defined, not to parent management groups or unrelated sibling branches of the hierarchy.

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

No community discussion yet for this question.