Associate Cloud Engineer ยท Billing, locations and environment tooling
Billing export to BigQuery
Exporting billing data to BigQuery (standard, detailed usage, pricing), what each export contains, and querying cost by project or label.
Key points
- Cloud Billing can export data to a BigQuery dataset, queried with SQL by project or label.
- Standard usage cost: account-level cost by service, SKU, project, label and location, with credits.
- Detailed usage cost: adds resource-level rows (e.g. one VM), can be costlier to query.
- Pricing: SKU price list and tiers.
- Pricing is not retroactive; usage backfill depends on the dataset location.
Source: https://docs.cloud.google.com/billing/docs/how-to/export-data-bigquery
Practice questions
Which billing export includes cost data at the level of individual resources, such as a specific VM?
- Standard usage cost
- Detailed usage cost
- Pricing
- Budget notifications
Show answer
Answer: B. Detailed usage cost
Detailed usage cost adds resource-level data on top of the standard export. Pricing holds list prices, not your spend.
Which data does the standard usage cost export contain?
- Services and SKUs
- Projects and labels
- Cost of one specific VM instance
- Credits and adjustments
- Pricing tiers of every SKU
Show answer
Answer: A. Services and SKUs, B. Projects and labels, D. Credits and adjustments
It has services and SKUs, projects and labels, and credits. Resource-level rows belong to the detailed export and price tiers to the pricing export.
True or false: when you first enable the pricing export, it is backfilled with earlier prices.
Show answer
Answer: False
False. Pricing data is never backfilled; it covers only the period from setup onward.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
