Your company needs to segment Google Cloud resources used by each team from the others. The teams' efforts are changing frequently, and you need to reduce operational risk and maintain cost…

The correct answer is A. One project per team. Google recommends using one project per team as the primary unit of resource isolation, IAM boundary, and cost tracking. Projects provide natural billing separation (visibility per team), independent IAM policies (reducing operational risk from cross-team permission bleed), and…

Google Cloud Resource Management and Hierarchy

Question

Your company needs to segment Google Cloud resources used by each team from the others. The teams' efforts are changing frequently, and you need to reduce operational risk and maintain cost visibility. Which approach does Google recommend?

Options

AOne project per team.
BOne organization per team.
COne project that contains all of each team's resources.
DOne top-level folder per team.

How the community answered

(41 responses)

A
93% (38)
B
5% (2)
C
2% (1)

Explanation

Google recommends using one project per team as the primary unit of resource isolation, IAM boundary, and cost tracking. Projects provide natural billing separation (visibility per team), independent IAM policies (reducing operational risk from cross-team permission bleed), and quota management. One organization per team would be extreme overkill and operationally complex. One shared project for all teams eliminates isolation. While top-level folders organize projects hierarchically, they do not themselves provide billing isolation or granular IAM boundaries the way projects do.

Topics

#Google Cloud Projects#Resource Hierarchy#Cost Management#Operational Risk Management

Community Discussion

No community discussion yet for this question.

Full CLOUD-DIGITAL-LEADER Practice