Prepare and test your skills

Prepare and test your skills

Implementation and data validation procedures are the steps that turn on automatic billing exports and prove the data arrives correctly for reporting. Cloud Billing (opens in a new tab) sends detailed billing data from a Cloud Billing account to a BigQuery (opens in a new tab) dataset automatically throughout the day. Data flows from the Cloud Billing account to the BigQuery dataset you specify, then from BigQuery to analysis, reporting, and visualization tools.
Cloud Billing account sends standard, detailed and pricing exports automatically throughout the day to a BigQuery dataset in a FinOps project, which then feeds SQL validation queries, reports, dashboards and JSON export.
Enabling automatic export to BigQuery creates a continuous transfer of usage, cost estimates, and pricing data for detailed analysis. The export is configured from the Billing export page in the Google Cloud console for each Cloud Billing account. The same dataset can hold standard usage cost data, detailed usage cost data, and pricing data, and the exported data can also be exported to a JSON file. Enable export at the same time you create each Cloud Billing account, because data is not backfilled for the period before export is enabled.
Exam tip: Billing data starts flowing only after export is enabled — earlier usage is never backfilled, so enable export before customer traffic begins.
Preparing the destination ensures the BigQuery dataset belongs to the correct project and billing account before export is turned on. The dataset is contained within a Google Cloud project (opens in a new tab) you choose, often a FinOps or billing administration project, and that project must have billing enabled and be linked to the same Cloud Billing account that holds the data to be exported. The service depends on all of these links: the API runs in the dataset project, the dataset lives in the billing-enabled project, and the project connects to the source billing account.
roles/resourcemanager.projectCreator).Validating delivery in BigQuery proves that rows from the Cloud Billing account have landed in the destination table and are ready for tools. Validation opens the exported table in BigQuery, runs a query that sums costs, and checks that expected projects, labels, and time ranges appear. Successful results mean the automated transfer from the Cloud Billing account to the BigQuery dataset is working and the data can feed reports and dashboards.
labels.value and SUM(cost) grouped by tenant, project, or service, with filters such as labels.key and usage_start_time for a monthly check.Selection of export types and data granularity is the choice of which Cloud Billing export to enable in BigQuery based on how much detail the analysis requires. Cloud Billing (opens in a new tab) export to BigQuery (opens in a new tab) automatically transfers billing data throughout the day from a Cloud Billing account to a BigQuery dataset that you specify. The exported data can then be queried in BigQuery for detailed analysis or exported to a JSON file. Enable the export on each Cloud Billing account at the same time you create the account so a complete dataset is available when analysis begins.
Standard usage cost data is the base-level billing export for invoice totals, cost trends, and project-level review. Standard usage cost data includes usage and cost estimates that support queries such as the sum of all costs per invoice, details by cost type per invoice month, and costs and credits by project for a specified invoice month. The data flows from the Cloud Billing account to the BigQuery dataset for reporting on what was spent and when. Choose standard usage cost data when the question is about total spend, invoice reconciliation, or trends rather than which individual resource created the cost.
Detailed usage cost data is a superset of standard usage cost data with additional fields for granular, resource-level cost analysis. Detailed usage cost data contains everything in the standard export plus fields that identify the specific resource that generated usage, such as a virtual machine or SSD. Labels flow with their resources into BigQuery, so costs can be grouped by label key and value to measure a service, environment, or cost center. Choose detailed usage cost data when the analysis must trace cost to an individual resource, such as summing costs for each resource per invoice or breaking down Google Kubernetes Engine (GKE) cluster costs.
Pricing data is the export that describes unit prices separately from measured usage and cost. Pricing data provides list prices for specific stock keeping units (SKUs), including service descriptions and product taxonomy and geo taxonomy for finding SKUs by product or region. Pricing data can be joined with detailed usage cost data in BigQuery to compare billed cost against list price and evaluate savings and optimization options. Choose pricing data when the question is about the price of a SKU itself rather than how much of that SKU was consumed.
Choosing the right export means matching the granularity of the export to the granularity of the cost question. The three exports differ in what they contain and when each one is useful, so use the level of detail in the cost question as the decision rule.
| Export type | Granularity and contents | Choose when |
|---|---|---|
| Standard usage cost | Aggregated usage and cost estimates for invoices, cost types, and projects | You need invoice totals, trends, or project-level costs and credits |
| Detailed usage cost | All standard fields plus resource-level fields, labels, and tags | You need to attribute cost to a specific resource, label, or GKE cluster |
| Pricing data | SKU list prices with service description and product and geo taxonomy | You need unit prices or want to join prices with usage costs for optimization |
Enable the needed exports before the project receives customer traffic because BigQuery billing data is not backfilled for the period before exporting is enabled.
Exam tip: Detailed usage cost data includes everything in standard usage cost data plus resource-level fields, so select the detailed export when analysis requires costs for an individual virtual machine, disk, or cluster.
Destination configuration and permission requirements define who can turn on billing export and where the exported data can live. Cloud Billing (opens in a new tab) export to BigQuery (opens in a new tab) automatically sends detailed billing data, such as usage, cost estimates, and pricing data, throughout the day to a BigQuery dataset you specify. Data then flows from the Cloud Billing account to tables inside that dataset, where it can be queried for detailed analysis or exported to a JSON file. The export depends on both sides being ready: an identity with administrative access to the billing account and destination, and a prepared destination project and dataset to securely house the financial data.
Required permissions for billing export control who can enable the flow of financial data from a billing account to BigQuery. Identity and Access Management (IAM) ownership is required on both the source and the destination, shown in the documentation as the IAM Owner role (roles/owner) on the project holding the data and on the linked Cloud Billing account. Selecting an existing destination project does not require a specific IAM role beyond already having a role on that project, while creating a new project requires the Project Creator role (roles/resourcemanager.projectCreator), which contains the resourcemanager.projects.create permission. Because exported billing data is sensitive, only trusted administrators with account-level access can configure the destination and turn on the export.
Preparing the destination project and dataset creates the secure container that will receive billing data before export is enabled. The destination dataset lives inside a Google Cloud project (opens in a new tab) you choose, and datasets organize and control access to the exported tables and views. The workflow depends on order because BigQuery requires the dataset to exist before Cloud Billing can write to it, and the destination project must be linked to the same billing account that is the source of the data.
Destination rules and timing limits determine whether export will succeed and how complete the data will be. The destination dataset cannot use customer-managed key encryption and cannot use an unsupported region location, so an existing dataset must be checked against those limits before use. Timing is also critical because export only sends data forward from the time it is enabled and does not backfill data from before exporting was enabled. To keep a complete dataset for analysis, enable Cloud Billing data export to BigQuery on each Cloud Billing account at the same time you create the account and before the project receives customer traffic.
Exam tip: Billing export does not backfill history, so data from before export was enabled will never appear in BigQuery.
Enable Cloud Billing export to BigQuery at the same time you create each Cloud Billing account and before the project receives customer traffic. Billing data starts flowing only after export is enabled and data from before export was enabled is never backfilled into BigQuery.
Standard usage cost data is the base-level export for invoice totals, cost trends, and project-level review, including usage and cost estimates by invoice and project. Detailed usage cost data contains everything in standard usage cost data plus resource-level fields, labels, and tags for tracing cost to a specific resource such as a virtual machine or SSD. Choose detailed usage cost data when analysis must attribute cost to an individual resource, label, or Google Kubernetes Engine (GKE) cluster.
Use Cloud Billing pricing data export to BigQuery when the cost question is about unit prices for stock keeping units (SKUs) rather than measured usage and cost. Pricing data provides list prices for specific stock keeping units (SKUs), including service descriptions and product taxonomy and geo taxonomy for finding SKUs by product or region. Pricing data can be joined with detailed usage cost data in BigQuery to compare billed cost against list price and evaluate savings and optimization options.
Enabling Cloud Billing export to BigQuery requires Identity and Access Management (IAM) ownership on both the source Cloud Billing account and the destination project holding the data, and creating a new project requires the Project Creator role. The destination BigQuery dataset must already exist in a Google Cloud project that has billing enabled and is linked to the same Cloud Billing account being exported, and the BigQuery Data Transfer Service API must be enabled in that project when exporting pricing data. The destination dataset cannot use customer-managed key encryption and cannot use an unsupported region location.
Your company is implementing a financial monitoring and FinOps optimization strategy across its Google Cloud organization. The cloud operations team needs to analyze cloud spending at the individual resource level, including examining costs generated by specific Compute Engine virtual machine instances and evaluating custom resource labels.
Which Cloud Billing export should you configure to send this level of granular data to BigQuery?
Last updated