A state IT office must oversee many county Azure subscriptions under one governance tree while counties keep their own subscriptions. Which Azure feature fits that multi-subscription hierarchy?
Select an answer to reveal the explanation.
Short Explanation
Think org chart for cloud accounts: management groups are the branches, subscriptions are the offices hanging under them. Counties keep their own subscriptions; the state hangs governance higher on the tree.
Full Explanation
A state IT office that must oversee many county Azure subscriptions under one governance tree, while counties keep their own subscriptions, needs management groups. Management groups nest subscriptions under a shared hierarchy so policy and access can be applied at higher nodes and inherited by the county subscriptions beneath them. That pattern preserves county billing and workload boundaries while giving the state a coherent governance roof.
Availability sets group virtual machines for fault and update domain redundancy inside a datacenter concept; they do not merge county invoices or organize subscriptions. A single resource group cannot span unlimited subscriptions by design—each resource group lives in one subscription—so it cannot be the multi-subscription hierarchy. Azure Bastion provides secure RDP/SSH connectivity into VMs; it is not a subscription-grouping construct.
Exam caveat: there is a root management group for a tenant, and depth and moving subscriptions between management groups have administrative prerequisites—plan ownership and change windows before large reorganizations. Operational check: map counties to subscriptions, place those subscriptions under regional or state management-group nodes that match the civic org chart, and validate a read-only policy assignment at the state parent appears in compliance views for a sample county child.