Your organization runs many workloads in different Google Cloud projects, each linked to the same billing account. Each project's workload costs can vary from month to month, but the overall combined

Question

Options

• APurchase a commitment per project for each project's usual minimum
• BCreate a billing account per project, and link each project to a different billing account
• CTurn on committed use discount sharing, and create a commitment for the combined usage
• DMove all workloads from all different projects into one single consolidated project

• A
  7% (4)
• B
  17% (10)
• C
  73% (43)
• D
  3% (2)

Explanation

When the combined cost across all projects is stable but individual project costs vary, the best optimization strategy is to enable committed use discount (CUD) sharing at the billing account level and purchase a single commitment for the aggregate usage. CUD sharing allows one commitment to cover resources across all linked projects, maximizing discount utilization. Buying per-project commitments (A) wastes money when a project's usage dips below its committed minimum. Creating separate billing accounts per project (B) prevents discount sharing and increases overhead. Consolidating all workloads into one project (D) is an organizational anti-pattern that breaks isolation and access control.

No community discussion yet for this question.