Question

Difficulty: EasyOptimizing Business Processes through FinOps and Cloud Cost Management

A financial operations (FinOps) team is establishing cloud cost governance and visibility across an organization's Google Cloud environment. Which of the following recommendations represent valid GCP cost optimization and billing governance practices? (Select TWO options.)

  1. Export Cloud Billing data to BigQuery to enable granular cost analysis and custom visualization dashboards.Answer
  2. Configure Cloud Billing budgets with programmatic Pub/Sub notifications to alert teams when spent thresholds are reached.Answer
  3. C
    Purchase 3-year Committed Use Discounts (CUDs) for newly launched, highly unpredictable short-term microservice workloads.
  4. D
    Migrate standard low-traffic relational databases from Cloud SQL to Cloud Spanner to reduce overall database operational costs.
  5. E
    Assign the primitive Owner role to department engineers so they can directly edit billing accounts and view costs.

Answer

The correct practices are exporting Cloud Billing data to BigQuery for granular cost reporting and configuring Cloud Billing budgets with programmatic notifications to alert teams of spending thresholds.
Exporting Cloud Billing data to BigQuery enables deep custom analytics, trend reporting, and cost allocation visualizations across projects. Combining this with Cloud Billing budgets and Pub/Sub notifications ensures proactive alerting when spending approaches specified financial limits.

Step-by-Step Solution

1
Analyze FinOps governance requirements for cost visibility and proactive budgeting.
Identified BigQuery billing export as the standard tool for detailed cost analysis and custom reporting, and Billing Budgets with alerts as the key mechanism for cost control.
Effective FinOps requires granular data for analysis alongside automated alerting to prevent cost overruns.
2
Evaluate the commitment model for variable workloads.
Rejected long-term Committed Use Discounts for unpredictable short-term workloads.
CUDs require predictable baseline usage to deliver financial savings; applying them to fluctuating workloads creates unutilized commitments.
3
Evaluate resource selection and IAM privileges.
Rejected using Cloud Spanner for simple relational workloads and rejected primitive Owner roles.
Cloud Spanner incurs high baseline costs unsuited for small workloads, and primitive IAM roles violate least privilege governance.

Key Concept

GCP Cloud Billing Export and Budget Governance
Rate this question