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.
A data platform team operates large-scale ELT pipelines and BigQuery analytics workloads across multiple Google Cloud projects. The team needs to establish a proactive cost governance and monitoring strategy to satisfy the following requirements:
Which architecture and configuration should the team implement?
This configuration exports Detailed usage cost data to BigQuery, points Looker Studio directly at the raw billing table, and deploys a custom serverless function to estimate storage costs via INFORMATION_SCHEMA.TABLE_STORAGE.
gcp_billing_export_resource_v1_* table without an intermediary BigQuery view exposes dashboards to breaking errors when Google updates table columns.INFORMATION_SCHEMA.TABLE_STORAGE only reflects BigQuery storage usage, entirely missing compute slot costs, network egress, and other Google Cloud services. Furthermore, INFORMATION_SCHEMA queries omit adjustments, taxes, and negotiated discount credits, making total budget forecasting inaccurate.The workload was solely concerned with monitoring raw physical table bytes in BigQuery rather than overall multi-service cloud expenditures.
This approach uses the Standard usage cost export to BigQuery, attempts to enforce storage security using Customer-Managed Encryption Keys (CMEK), queries the raw export table directly from Looker Studio, and uses Cloud Monitoring metric thresholds for alerts.
The organization required high-level SKU aggregations only and relied entirely on Google-managed encryption keys while monitoring simple trailing threshold breaches.
This architecture establishes an enterprise-grade FinOps pipeline by streaming Detailed usage cost data into BigQuery, abstracting data consumption through BigQuery views, visualizing trends in Looker Studio, and applying predictive cost threshold alerts via Cloud Billing budgets.
gcp_billing_export_resource_v1_ table, capturing granular resource identifiers (such as VM instances, GKE namespaces, and SSDs) necessary for micro-level workload attribution.Directly querying raw export tables creates tight coupling and fragility against upstream schema evolution. Utilizing BigQuery views provides maintainability and standardization, while native forecasted budget alerts eliminate the need for custom, error-prone forecasting pipelines.
This architecture exports pricing and standard usage data to Cloud Storage JSON objects, processes the files into BigQuery using an intermediate Dataflow pipeline, and configures Cloud Billing budget alerts based on actual invoiced spend.
External compliance regulations required raw JSON staging in an external storage system prior to data warehouse ingestion and only retrospective actual-spend audits were needed.
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