A customer's company has multiple business units. Each business unit operates independently, and each has their own engineering group. Your team wants visibility into all projects created within the…

Question

Options

• ACreate an organization node, and assign folders for each business unit.
• BEstablish standalone projects for each business unit, using gmail.com accounts.
• CAssign GCP resources in a project, with a label identifying which business unit owns the
• DAssign GCP resources in a VPC for each business unit to separate network access.

• A
  88% (28)
• B
  6% (2)
• C
  3% (1)
• D
  3% (1)

Explanation

Google Cloud's resource hierarchy - Organization → Folders → Projects → Resources - is designed exactly for this use case. Creating an Organization node provides a single point of visibility across all projects. Creating a Folder per business unit allows separate IAM policies at the folder level (inherited by all child projects), centralized billing visibility, and independent administration for each engineering group. Option B (standalone projects with Gmail accounts) loses centralized visibility and control, and Gmail accounts should not be used for corporate GCP. Option C (resource labels) provides metadata tags but does not enforce separate IAM boundaries. Option D (separate VPCs) addresses network isolation only, not IAM permissions or project organization.

No community discussion yet for this question.