Examkin

Question

Difficulty: HardManaging Resource Quotas, Hierarchies, and Cost Optimization

A healthcare enterprise manages a multi-tenant Google Cloud organization structured into multiple environment folders. The central FinOps team must implement centralized billing analysis across all projects, automate real-time budget threshold notifications to an external Slack channel, and enforce strict governance over quota requests and billing settings across business units. Which TWO actions should the Cloud Architect recommend to satisfy these requirements?

  1. Enable detailed billing data export at the Cloud Billing Account level to stream all project billing data into a central administration project's BigQuery dataset.Answer
  2. Attach a Cloud Pub/Sub topic to Cloud Billing Budgets at the Billing Account level, and deploy a Cloud Run service using least-privilege IAM roles to process budget messages and forward them to Slack.Answer
  3. C
    Grant the Owner primitive IAM role at the folder level to business unit leads so they can configure project-level BigQuery billing exports and manage regional quota requests independently.
  4. D
    Configure CI/CD deployment pipelines to dynamically submit regional Compute Engine quota increase requests via gcloud commands immediately prior to provisioning new compute instances.

Answer

The Cloud Architect should enable detailed billing data export at the Cloud Billing Account level to a central BigQuery dataset, and attach a Cloud Pub/Sub topic to Cloud Billing Budgets to trigger a least-privilege Cloud Run service for automated Slack alerts.
Centralizing billing data export at the Cloud Billing Account level provides complete organizational cost visibility without delegating access to project-level teams. Connecting Cloud Billing Budgets to Cloud Pub/Sub allows secure, event-driven processing of threshold notifications via Cloud Run without exposing sensitive credentials or using elevated IAM permissions.

Step-by-Step Solution

1
Centralize billing data aggregation.
Configuring export at the Billing Account level ensures all linked project billing records stream automatically to a centralized BigQuery dataset managed by the central FinOps team.
This avoids granting project-level export permissions to business unit teams and guarantees complete organizational visibility.
2
Automate billing budget alerts securely.
Publishing budget threshold alerts to Cloud Pub/Sub enables event-driven integration with Cloud Run.
Serverless consumers running with service accounts adhere to least-privilege access rules while ensuring reliable real-time notifications.
3
Avoid anti-patterns regarding roles and quota timing.
Rejecting primitive roles and reactive pipeline quota requests prevents security vulnerabilities and deployment pipeline failures.
Quota increases require lead time for approval and should be pre-provisioned, while IAM governance demands custom or predefined roles.

Key Concept

Centralized Cloud Billing governance, BigQuery billing export, Pub/Sub budget automation, and proactive quota planning.
Rate this question

Topics

Managing Resource Quotas, Hierarchies, and Cost Optimization