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
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?
Enable Standard usage cost data export to a BigQuery dataset configured with Customer-Managed Encryption Keys (CMEK). Connect Looker Studio directly to the standard export table, and configure Cloud Monitoring metric-based alerts on daily billing metrics.
Enable Detailed usage cost data export directly to BigQuery. Connect Looker Studio directly to the raw table, and implement a scheduled Cloud Run function querying INFORMATION_SCHEMA.TABLE_STORAGE to forecast costs and trigger alerts.
Enable Pricing data export and Standard usage export to Cloud Storage in JSON format. Use Dataflow to process and write the JSON files into BigQuery, and set up Cloud Billing budget alerts based strictly on actual invoice-month spend.
Enable Detailed usage cost data export to a BigQuery dataset within a dedicated billing project. Create BigQuery views over the exported table to normalize the schema for Looker Studio, and configure Cloud Billing budget alert threshold rules triggered against forecasted costs.
Enable Standard usage cost data export to a BigQuery dataset configured with Customer-Managed Encryption Keys (CMEK). Connect Looker Studio directly to the standard export table, and configure Cloud Monitoring metric-based alerts on daily billing metrics.
Enable Detailed usage cost data export directly to BigQuery. Connect Looker Studio directly to the raw table, and implement a scheduled Cloud Run function querying INFORMATION_SCHEMA.TABLE_STORAGE to forecast costs and trigger alerts.
Enable Pricing data export and Standard usage export to Cloud Storage in JSON format. Use Dataflow to process and write the JSON files into BigQuery, and set up Cloud Billing budget alerts based strictly on actual invoice-month spend.
Enable Detailed usage cost data export to a BigQuery dataset within a dedicated billing project. Create BigQuery views over the exported table to normalize the schema for Looker Studio, and configure Cloud Billing budget alert threshold rules triggered against forecasted costs.
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.
StudyCerts
StudyCertsgcp_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.