In Azure, you want to organize multiple subscriptions under a management group hierarchy. Which statement correctly describes the relationship between management groups and subscriptions?
Think about how Azure organizes resources for governance and policy application.
Management groups form a hierarchy where each management group can contain subscriptions and other management groups, allowing centralized management.
You manage an organization with multiple departments. You want to separate billing and policies per department but keep centralized control. Which Azure structure best supports this?
Consider how billing and policy boundaries work in Azure.
Separate subscriptions per department allow distinct billing and resource limits, while management groups enable centralized policy and access control.
You want to enforce a security policy that restricts VM sizes across all subscriptions in your organization. Where should you assign this policy for the most efficient management?
Think about applying policies once to affect many subscriptions.
Assigning the policy at the management group level applies it to all subscriptions under it, simplifying management and ensuring consistency.
You move a subscription from one management group to another. What immediate effect does this have on the subscription's policy and access control?
Consider how inheritance works in Azure management groups.
When a subscription moves, it inherits policies and access controls from the new management group, which override previous ones.
Your enterprise has hundreds of subscriptions across multiple regions and business units. What is the best practice for structuring management groups to balance governance, scalability, and ease of management?
Think about balancing complexity and manageability in large organizations.
A balanced hierarchy grouping by business unit and region with limited nesting helps maintain clarity, scalability, and effective governance.