Contoso uses the management group hierarchy of the Azure landing zone reference architecture. An internal line-of-business app must connect to the corporate network through the hub in the connectivity subscription. The development, test, and production environments must be separated but receive the same security policies, and the app's workload team must be able to deploy resources only to its own app environments and have no permissions on other workloads. Which design should you recommend?
Show answer and explanation
Answer: B
Explanation
Workloads that require connectivity or hybrid connectivity with the corporate network through the hub belong in the Corp management group.[1] Don’t create management groups for production, testing, and development environments; if necessary, separate them into different subscriptions in the same management group.[1] Management groups are used to assign Azure policies to all subscriptions that require the same security, governance, and compliance settings, so all three environments receive the same policies.[1] Workload team permissions are assigned at the individual subscription or resource group scopes they need, normally during the subscription vending process, so the team gets no permissions on other workloads.[1]
Environment-specific management groups go against the recommendations, and workload team RBAC at management group scope isn’t recommended either.[1] The Sandboxes management group is for testing and exploration, has a less restrictive set of policies, and is isolated from the corporate landing zones, so development and test wouldn’t receive the same policies as production.[1] Assigning workload team RBAC at the Corp management group scope lets permissions inherit to every subscription under it, which causes over-permissioning and security risk.[1]