CLOUD-DIGITAL-LEADER practice question 1 of 35

Your organization needs to ensure that the Google Cloud resources of each of your departments are segregated from one another. Each department has several environments of its own: development, testing, and production. Which strategy should your organization choose?

Full set: 411 questions
Answer options
A: Create a project per department, and create a folder per environment in each project.
B: Create a folder per department, and create a project per environment in each folder. Correct answer
C: Create a Cloud Identity domain per department, and create a project per environment in each domain.
D: Create a Cloud Identity domain per environment, and create a project per department in each domain.
Correct Answer:
B. Create a folder per department, and create a project per environment in each folder.
Explanation

Google Cloud’s recommended hierarchy is Organization → Folder(s) → Project(s). Create one top-level folder for each department to hard-separate their policies, IAM, and billing. Inside each department folder, create separate projects for the dev, test, and prod environments; projects are the smallest isolation and quota boundary, so environment-specific projects prevent accidental cross-environment impact while inheriting the department’s folder-level policies. Folders cannot exist inside projects, and multiple Cloud Identity domains per department or per environment is unnecessary and adds administrative overhead; therefore, the folder-then-project pattern is the correct strategy.

Why Incorrect

A. Folders cannot be created inside projects; hierarchy is Organization→Folder→Project, not Project→Folder.
C. A Cloud Identity domain maps 1-to-1 with the entire organization; multiple domains for departments violate recommended practice and add cost/complexity.
D. Same domain misuse as C, plus projects would mix departments inside a domain, defeating segregation.

References

1. Google Cloud documentation, “Designing and Building Your Resource Hierarchy”, Section “Use folders for departments or teams” & Figure 1 hierarchy example (cloud.google.com/resource-manager/docs/creating-managing-folders).

2. Google Cloud Resource Manager Docs, “Folders Overview”, para. 2: “Folders can contain projects… folders cannot be created inside projects.”

3. Google Cloud Identity Overview, “Relationship of Cloud Identity and Organization resource”: single domain represents the organization (cloud.google.com/identity/docs/concepts).

4. Google Cloud Architecture Center, “Enterprise Foundations blueprint – Organizing Resources”, Step 2: “Create top-level folders for each business unit, then create environment-specific projects.”

Scroll to Top