Google Professional Cloud Security Engineer Question 163
Single answerGoogle Cloud PlatformYou are designing a Google Cloud resource hierarchy for a multinational organization. The organization has multiple business units, each operating in different regions, and requires strict separation of administrative control, billing, and compliance for each unit. Which approach should you take to define the resource hierarchy in Google Cloud?
- A
Create a single organization node and use folders under it to represent each business unit.
- B
Create separate organization nodes for each business unit to isolate resources and billing.
- C
Use a single project per region to manage all resources for each business unit.
- D
Create a shared folder for all business units and use labels on resources to manage separation.
Show answer and explanation
Correct answer: A
Explanation
The correct approach is to use a single organization node and create folders under it for each business unit. Folders allow you to group projects and resources hierarchically while enforcing specific access controls, compliance requirements, and billing configurations at the folder level. This approach ensures isolation for each business unit while maintaining centralized management at the organization level.
- A. Correct.
Using a single organization node with folders for each business unit allows you to enforce administrative and compliance boundaries while maintaining centralized billing and overall management. This approach aligns with Google Cloud best practices for resource hierarchy.
- B. Incorrect.
Google Cloud supports only one organization node per domain, so creating separate organization nodes for each business unit is not possible.
- C. Incorrect.
Using a single project per region does not provide the level of separation and administrative control required for this scenario. Projects are better suited for grouping resources with shared lifecycles rather than separating business units.
- D. Incorrect.
Using a shared folder for all business units with labels does not enforce strict separation of administrative control, making it unsuitable for the organization's requirements.