Google Professional Cloud DevOps Engineer Question 2
Single answerGoogle Cloud PlatformYou are a DevOps engineer tasked with designing the Google Cloud resource hierarchy for a new organization. The organization has multiple departments (Engineering, Marketing, and Sales), each requiring its own isolated billing and access controls. Additionally, the company plans to deploy multiple projects in each department. What is the most appropriate way to design the resource hierarchy?
- A
Create a single organization node, split departments into folders under the organization node, and create projects within each folder.
- B
Create separate organization nodes for each department to ensure isolation, and create projects under each organization node.
- C
Create a single organization node and directly create projects for each department under the organization node.
- D
Create a separate folder for billing and another folder for access controls, and place all projects under these folders.
Show answer and explanation
Correct answer: A
Explanation
In Google Cloud, the resource hierarchy starts with a single organization node, which represents the root of all resources in a company. Folders are used to logically group resources, such as by department or team, and projects are created within these folders. This approach provides a clear structure for managing billing and access controls at the folder level, ensuring isolation between departments while adhering to Google Cloud best practices.
- A. Correct.
This is the correct approach. A single organization node serves as the root of the hierarchy, folders provide a logical grouping for departments, and projects can be created within folders. This allows for billing and access controls to be managed at the folder level.
- B. Incorrect.
This is incorrect because an organization is a global root node for all resources in a company. You cannot create multiple organization nodes for a single company.
- C. Incorrect.
This is incorrect because directly creating projects under the organization node does not provide sufficient isolation or grouping for managing billing and access controls at the department level.
- D. Incorrect.
This is incorrect because folders are not designed to separate billing and access controls independently. Instead, folders should represent logical entities, such as departments or teams.