Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
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?
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.
k8s-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.
This option involves attaching static Google Cloud resource labels to the underlying GKE Compute Engine worker nodes, tracking aggregate spending on the Billing Overview page, and using role-based email alerts to trigger manual cluster shutdowns.
Each GKE node hosted a single dedicated workload with no multi-tenancy and the organization preferred manual incident handling rather than automated workload remediation.
This approach suggests using the standard usage cost export to BigQuery to analyze GKE allocation data and relying on a built-in hard spending cap in the Cloud Billing Console to terminate resources when spending exceeds 120% of the budget.
Google Cloud offered native hard-cap enforcement switches directly within the Budget UI and standard BigQuery export included fine-grained Kubernetes namespace telemetry.
This option suggests using Cloud Monitoring notification channels for budget emails, reviewing SKU rates with the Pricing Table report, and using Cloud Logging alerts to disable the entire Cloud Billing account.
The goal were to audit contract discounts against list prices and enforce an emergency kill-switch across the entire company portfolio upon critical security or policy violations.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated