Google Professional Cloud Architect
Get started today
Ultimate access to all questions.
Ultimate access to all questions.
Your company has a Google Workspace account and Google Cloud Organization. The organization has various teams, including developers who need to create and manage Google Cloud projects. However, some developers have created projects outside of the official Google Cloud Organization, leading to issues with policy management and control. You want to establish an Organization structure that allows developers the flexibility to create projects but ensures they cannot modify production projects. Centralized policy management is crucial to maintain consistency, with the ability to enforce stricter policies on production projects. This structure should also minimize disruption to users and developers when there are changes in business needs. Following Google-recommended practices, how should you design the Organization structure to achieve these goals?
Explanation:
The correct answer is C. Creating separate folders under the Organization resource named 'Development' and 'Production' aligns with Google-recommended practices. This structure allows developers to create projects within the 'Development' folder while still enabling centralized management of policies across all projects within the organization. Additionally, the 'Production' folder can have more restrictive policies applied, which meets the requirement of preventing modifications to production projects. This approach also minimizes disruption when business needs change, as projects can easily be moved between folders without changing their organizational structure. Managing multiple organizations, as suggested in other options, would introduce unnecessary complexity and make it more difficult to centrally manage policies.