professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise data engineering team operates a multi-tenant Google Kubernetes Engine (GKE) cluster and several automated data pipelines distributed across multiple projects linked to a single Cloud Billing account. During the last billing cycle, the finance department detected an unexpected cost spike in compute and persistent storage resources.
The team must implement a solution that satisfies the following operational requirements:
Which combination of actions should the team implement?
Configure project-level budgets with Cloud Monitoring email notification channels, enable the Pricing Table report to audit SKU rates, and configure Cloud Logging alerts to automatically disable the Cloud Billing account upon threshold violation.
Apply user labels directly to the Compute Engine node VMs in the console, view the Cloud Billing Overview page, and rely on standard Cloud Monitoring alert emails sent to Billing Administrators to manually shut down clusters.
Enable GKE cost allocation on the cluster, configure Cloud Billing standard usage cost export to BigQuery, and configure a hard budget cap rule in the Cloud Billing Console to automatically shut down project resources at 120% spend.
Enable GKE cost allocation on the cluster, configure Cloud Billing detailed usage cost export to BigQuery to query costs by namespace and workload labels, and attach a Pub/Sub programmatic notification to the budget to trigger automated remediation workloads.
Configure project-level budgets with Cloud Monitoring email notification channels, enable the Pricing Table report to audit SKU rates, and configure Cloud Logging alerts to automatically disable the Cloud Billing account upon threshold violation.
Apply user labels directly to the Compute Engine node VMs in the console, view the Cloud Billing Overview page, and rely on standard Cloud Monitoring alert emails sent to Billing Administrators to manually shut down clusters.
Enable GKE cost allocation on the cluster, configure Cloud Billing standard usage cost export to BigQuery, and configure a hard budget cap rule in the Cloud Billing Console to automatically shut down project resources at 120% spend.
Enable GKE cost allocation on the cluster, configure Cloud Billing detailed usage cost export to BigQuery to query costs by namespace and workload labels, and attach a Pub/Sub programmatic notification to the budget to trigger automated remediation workloads.
This architecture combines GKE cost allocation, Cloud Billing detailed usage cost data export to BigQuery, and Cloud Billing programmatic notifications via Pub/Sub to provide fine-grained cost attribution and automated spend remediation.
StudyCerts
StudyCertsk8s-namespace and custom Pod labels). These metrics are written to BigQuery exclusively through the detailed usage cost data export, allowing analysts and engineers to run SQL queries that aggregate costs by tenant, namespace, or workload.Standard billing reports and exports only provide project-level or VM-level breakdowns, failing to isolate multi-tenant Kubernetes workloads. Programmatic notifications bridge the gap between passive alerting and active cost governance.