Google ACE Setting Up a Cloud Solution Environment Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Enable Cloud Billing API

  Why it's wrong here

  The Cloud Billing API is designed for programmatic access to billing account metadata, budgets, and invoice information, not for configuring data exports. When you set up billing export in the Cloud Console, the export job is created automatically and uses BigQuery's storage write APIs; enabling the billing API is neither necessary nor sufficient. You could enable that API in an unrelated project and still have no billing export.

• ✗

  Create a Cloud Storage bucket

  Why it's wrong here

  Although Cloud Storage is one of the allowed destinations for billing export, it stores raw JSON/CSV files that are not directly queryable with SQL. For detailed analysis, BigQuery is the correct destination because it creates columnar tables that you can query with standard SQL. Moreover, simply creating a bucket does nothing unless you also configure the export in billing settings, and choosing a bucket would be a different integration than the BigQuery one.

• ✓

  Create a BigQuery dataset

  Why this is correct

  Creating a BigQuery dataset is the necessary container that receives the exported billing tables. When you configure billing export, you must specify an already-existing dataset in the selected project; the export then creates and manages the underlying tables (e.g., `gcp_billing_export_v1_*`) within that dataset. Without a dataset, the billing export setup page in the Cloud Console will not allow you to proceed.

• ✓

  Set up billing export in the Cloud Console

  Why this is correct

  This is the central manual step: navigating to Billing → Billing export in the Cloud Console, choosing BigQuery as the destination, and selecting the dataset you created. It creates a scheduled job that periodically copies billing records into that dataset, providing up-to-date cost and usage data for SQL analysis. Without this configuration, no export will occur even if the dataset and BigQuery API are both ready.

• ✓

  Enable BigQuery API

  Why this is correct

  Enabling the BigQuery API (`bigquery.googleapis.com`) ensures that your project can run BigQuery jobs, and the billing export service depends on this API to write rows into the chosen dataset. If the API remains disabled, the export job will fail whenever it attempts to interact with BigQuery. This is a one-time activation per project, and while it is a required prerequisite, it does not by itself create the export.

Go deeper

Related to this question