CLOUD-DIGITAL-LEADER practice question 3 of 35

You are consulting for a client who is migrating to Google Cloud. They presently have a matrix or- ganization. Their IT environments were managed around projects. Each team had multiple projects. All the projects had a flat structure under the company. What would you advise them when plan-ning for the move?

Full set: 411 questions
Answer options
A: On Google Cloud, create a folder corresponding to each team. Under that, there could be projects or further sub folders as the team decides. Correct answer
B: In terms of not disturbing the project developers and testers, advise them that the strategic decision is to retain the structure on Google Cloud also.
C: Since a Project could spawn other sub-Projects, on Google Cloud it is better to as-sign a folder for each Project.
D: The flat structure is what is currently used in IT organizations, and this can be used as-is which will provide the best results.
Correct Answer:
A. On Google Cloud, create a folder corresponding to each team. Under that, there could be projects or further sub folders as the team decides.
Explanation

Google Cloud’s resource hierarchy is Organization ➝ Folder ➝ Project. Folders exist specifically to mirror an enterprise’s departmental or team structure and let administrators apply IAM and policies to whole teams, while individual workloads still live in separate projects. Because the client already works in a matrix where each team owns several projects, the closest—and Google-recommended—mapping is one folder per team with that team’s projects (or deeper sub-folders) nested below. This provides delegated administration, clearer billing, and policy inheritance without forcing a disruptive redesign of the teams or over-flattening the hierarchy.

Why Incorrect

B. Retaining a single-level project list ignores Google Cloud’s folder capability, impedes policy inheritance, and scales poorly for IAM/billing.
C. Projects cannot contain “sub-projects”; creating a folder for every project adds an unnecessary layer and still fails to group by team.
D. Flat structures hinder large-scale policy/billing management; Google documentation recommends folders for complex organizations.

References

1. Google Cloud Resource Manager: “Resource hierarchy overview – Use folders to group projects by business units, teams, or environments.” (Docs ID: resource-hierarchy-overview, §“Folders”, para. 2, 2023-10-18).

2. Google Cloud Resource Manager: “Creating and Managing Folders – Folders let you delegate administrative rights to different teams.” (Docs ID: managing-folders, §Overview, para. 1).

3. Google Cloud Architecture Framework – “Establish a hierarchy that reflects your org structure; apply policies at the folder level.” (Version 2.0, Governance section, pp. 5-6).

4. MIT Cloud Security course notes (6.S897, Spring 2023) – Lecture 3 slides, “GCP hierarchy: Org → Folder → Project; folders map to teams for IAM/billing delegation.”

Scroll to Top