A DevOps engineer is setting up a new Google Cloud organization for their company. They need to ensure that all projects are created within a structured hierarchy that separates production, staging, development, and sandbox environments. Which folder structure BEST supports this requirement?
Trap 1: Create a folder for each product under the organization node, and…
This makes it harder to apply organization-wide environment policies, as policies would need to be applied per product.
Trap 2: Create a flat folder structure under the organization node with one…
This mixes environments, making it harder to apply environment-specific policies.
Trap 3: Create a flat folder structure with one folder per project type…
This does not separate environments, which is critical for governance.
- A
Create a folder for each product under the organization node, and within each product folder, create subfolders for environments.
Why wrong: This makes it harder to apply organization-wide environment policies, as policies would need to be applied per product.
- B
Create a flat folder structure under the organization node with one folder per team, and place all projects in their team folder regardless of environment.
Why wrong: This mixes environments, making it harder to apply environment-specific policies.
- C
Create a folder for each environment (prod, staging, dev, sandbox) directly under the organization node. Within each environment folder, create subfolders for teams or products, and place projects in those subfolders.
This is the standard landing zone design that separates environments and allows inheritance.
- D
Create a flat folder structure with one folder per project type (shared VPC, logging, security) and place all projects in those folders.
Why wrong: This does not separate environments, which is critical for governance.