Prepare and test your skills

Prepare and test your skills

A Cloud Billing account (opens in a new tab) is the Google Cloud resource that pays for usage and tracks costs for linked projects. Usage costs flow from resources in a project to the linked Cloud Billing account, and payment for those costs flows through a connected Google payments profile. The Google payments profile holds payment instruments, billing contacts, and payment history, while the Cloud Billing account tracks which projects used what resources. A project must be linked to an active billing account in good standing, or the project cannot use Google Cloud services, even services that are otherwise free.
Every Cloud Billing account is connected to one Google payments profile, and each account operates in a single currency. Payments contacts are people designated to receive billing information about the payment instrument on file, such as when a credit card needs to be updated. These contacts can be viewed and managed in the Google payments center or in the Google Cloud console on the Payment settings and Payment method pages.
An organization resource plus the correct Identity and Access Management (IAM) roles are required before a billing account can be created. A company domain establishes identity with Google through Google Workspace or Cloud Identity (opens in a new tab), which automatically creates an organization resource tied to exactly one domain. Projects and billing accounts created under that domain become child resources of the organization, so IAM policies and organization policies inherit downward. Once the organization exists, a new billing account can be created from the Google Cloud console billing page and linked to one or more projects.
The creator must hold specific roles on the organization before creating billing:
Creation and management (opens in a new tab) are divided by scope because creation happens at the organization level while daily control happens at the billing account level. Billing Account Creator is granted on the organization and allows creation of new accounts inside that organization. Billing Account Administrator is normally granted on a specific billing account and allows management of settings, budgets, billing export, associations, and closing or reopening the account. Billing Account Viewer gives read-only visibility such as account name, currency, and open or closed state.
Linking a project to a billing account shows why permissions are checked on both sides. Data and control flow from the project to the billing account only after both checks pass: the caller needs billing.resourceAssociations.create on the billing account and resourcemanager.projects.createBillingAssignment on the project. Inheritance flows downward, so a role granted on the organization can affect billing accounts within that organization. Custom roles for billing are created on the organization and can then be applied to any billing account in that organization, such as a cost-management role with only budget and export permissions.
A billing account type defines who the account fits and how payment is collected. Most customers start with self-serve automatic payment, larger organizations may use monthly invoicing, and resellers use subaccounts to separate customer charges. All billing accounts within an organization use a single price sheet to charge service usage.
| Account type | Who it fits | How payment works |
|---|---|---|
| Self-serve account | Individual teams and smaller organizations | Pays automatically with an online payment method, such as a credit card or verified bank account |
| Invoiced billing account | Larger organizations with monthly billing | Receives a monthly invoice and pays by invoice |
| Cloud Billing subaccount | Resellers managing charges for customers | Behaves like a billing account with its own linked projects, exports, and IAM roles, but all charges are paid by the reseller's parent billing account and grouped on the invoice |
A subaccount allows access control to be fully separated per customer while keeping payment centralized with the parent account. One central Cloud Billing account is recommended because extra accounts add tracking overhead and reports show one billing account at a time. Multiple accounts are needed only for legal or accounting separation, for paying in multiple currencies, or for allocating support costs differently.
Exam tip: A parent Cloud Billing account must use invoiced billing to own subaccounts for resellers.
Continue with this study guide: Creating one or more billing accounts
Linking a project to a billing account connects two separate resources, so IAM checks permissions on both sides of the link. A Google Cloud project (opens in a new tab) is the container that holds resources such as virtual machines and storage buckets, while a Cloud Billing account defines who pays for usage in one or more projects. A user who has permission on only one side will see the Change billing or Disable billing option as unavailable in the Google Cloud console, and the user may need to reauthenticate before the change is allowed.
Establishing or changing the link requires create permissions on both resources at the same time. On the billing account, the permission is billing.resourceAssociations.create, held by Billing Account User and Billing Account Administrator. On the project, the permission is resourcemanager.projects.createBillingAssignment, held by Project Billing Manager and Project Owner. In practice, one person needs a billing role plus a project role together, most commonly Billing Account User plus Project Owner or Project Billing Manager.
Removing the link or unlocking a locked link requires delete permissions, but adequate permission on either side is sufficient. On the billing account, the permission is billing.resourceAssociations.delete, held by Billing Account Administrator. On the project, the permission is resourcemanager.projects.deleteBillingAssignment, held by Project Billing Manager or Project Owner. Viewing links also depends on side: billing.resourceAssociations.list on the billing account shows projects linked to that account, while resourcemanager.projects.get on projects shows the billing account linked to each project.
| Task | Billing account side | Project side |
|---|---|---|
| Link or change billing for a project | Billing Account User or Billing Account Administrator with billing.resourceAssociations.create | Project Billing Manager or Project Owner with resourcemanager.projects.createBillingAssignment |
| Unlock link or unlink to disable billing | Billing Account Administrator with billing.resourceAssociations.delete | Project Billing Manager or Project Owner with resourcemanager.projects.deleteBillingAssignment |
| View associations | Billing Account Viewer, Costs Manager, or Administrator with billing.resourceAssociations.list | Project Browser, Viewer, Editor, or Owner with resourcemanager.projects.get |
Exam tip: Linking a project requires permissions on both resources at once, while unlocking can be done with either the Billing Account Administrator role or the project-side Project Owner role.
The relationship between billing accounts and projects is one-to-many because one billing account can pay for many projects. Each project is linked to at most one Cloud Billing account (opens in a new tab) at a time, but that link can be changed to move the project to a different account. Payment linkage is flexible across organizations, so a billing account can pay for projects that belong to a different organization than the organization that owns the billing account.
Billing is enabled on a project only when two conditions are true at the same time. First, the project must be linked to a Cloud Billing account. Second, that linked account must be active and in good standing, meaning it is not closed or suspended. The console shows Billing is disabled for a project with no linked billing account, and resources in a project linked to a closed or suspended account cannot be used, even for services that are otherwise free.
Unlinking a billing account disables billing and stops the project from using its enabled products and services. By contrast, changing a project from one active billing account to another active billing account should not cause service interruption or downtime. Charges incurred before the change still belong to the former billing account, including charges not yet shown because services report usage at varying intervals with delays of up to two days.
Procedures for linking and modifying billing control which Cloud Billing account pays for a project and whether paid services can be used. Billing status can be checked on the My Projects page in Billing, which shows each project with its billing account name and ID, or for a single project with gcloud beta billing projects describe PROJECT_ID. Billing is enabled when the output contains a billingAccountName and billingEnabled: true, and billing is not enabled when the name is blank or billingEnabled: false.
How a new project gets linked depends on where the project is created, because different consoles handle billing differently. The Google Cloud console prompts (opens in a new tab) for a billing account or links the only available account automatically. The Firebase console starts the project unlinked on the no-cost Spark plan, and the Google AI Studio console starts the project unlinked on the Free tier for eligible models. For an existing project, enabling billing is done from the Billing page by selecting the project and linking an existing account or creating a new one.
Changing the linked account moves usage to a destination account without expected downtime:
A padlock icon means the link is locked and must be unlocked before it can be changed, and a locked link (opens in a new tab) uses the same create permissions as linking. Disabling billing unlinks the project by selecting Disable billing from the same Actions menu and confirming, but a locked link must be unlocked first. After disabling billing, prior usage is still billed to the previously linked account, so a move on May 15 bills May 1 to May 15 to the old account and later usage to the new account.
Continue with this study guide: Linking projects to a billing account
A Cloud Billing budget (opens in a new tab) is attached to a Cloud Billing account and filtered to include only selected projects, services, and other resource attributes. Costs flow from resources in linked projects to the Cloud Billing account, and the budget monitors the portion of that flow selected by its filters. Narrow scope gives granular tracking for one team or workload, while broad scope gives an organization-wide view. A realistic budget covers infrastructure costs, software licenses, and anticipated growth for each project, workload, and deployment environment.
Filtering lets one budget track a single project, one service such as Compute Engine or BigQuery, or a combination that matches a workload or environment. Labels provide resource-level filtering because a label is a key-value pair attached to a resource, and costs from labeled resources can be grouped by label key and value for a service, environment, or cost center. A formal labeling policy helps teams apply labels consistently, and automation tools such as Terraform can enforce labeling on every created resource. Exporting billing data to BigQuery supports custom, team-specific reports with fine-grained access control.
Granular control can be extended with quotas and limits, which work alongside budgets:
A spend cap budget is different from an alerts-only budget because it enforces a cap instead of only sending notifications. The spend cap budget applies to a single Google Cloud project and a single eligible service, its time range is automatically set to Monthly and cannot be edited, and savings settings also cannot be edited. When the cap is reached for Cloud Run, for example, services fail to serve traffic, new job executions fail to start, and worker pools stop processing tasks until the cap is lifted. An existing alerts-only budget cannot be converted, so it must be deleted and replaced with a new spend cap budget.
Alert thresholds decide when a budget sends a notification based on a percentage of the planned spend amount. A budget first sets a planned spend amount, and then one or more threshold rules define a percentage of that amount. When actual spend or forecasted spend crosses a threshold percentage, the budget triggers an alert to the configured recipients. For example, a 50% rule on a $1,000 budget fires at $500 and a 100% rule fires at $1,000.
Actual spend and forecasted spend measure different things and have different limits:
| Spend basis | What it measures | Key limitation |
|---|---|---|
| Actual spend | Costs already incurred in the current budget period | Subject to billing reporting delay |
| Forecasted spend | Projected total cost by end of the calendar period | Cannot be used with a custom time range |
Because of reporting delay, actual costs appear in Cloud Billing after resources are used, so it is recommended to set the budget amount below available funds. With a $100 budget and a 110% forecasted threshold, an alert fires when the projection shows spend will exceed $110 by the end of the period. After a budget is created, it can take several hours before the first notification arrives.
Default threshold rules notify at three percentages of the budget amount: 50% as an early warning, 90% as spend approaches the limit, and 100% as spend reaches the planned total. These defaults can be changed to match financial limits, with Add threshold to add rules and Delete to remove a row. An alerts-only budget only informs about spending trends and never automatically caps usage or stops spending when a threshold is met.
Exam tip: Budgets configured for a custom time range cannot trigger alerts on forecasted costs; use a monthly, quarterly, or yearly period for forecasted alerts.
Budget alerts are delivered by email for manual review or by Pub/Sub (opens in a new tab) for programmatic automation. Email notifications support manual oversight by sending a message to people when a spend threshold is met. Pub/Sub notifications support automated responses by sending budget status to code and integrations that can act on it. Both paths are set under Manage notifications, and alerts-only budgets only inform and never automatically cap usage.
Role-based email alerts send notifications based on IAM roles and require at least one threshold rule. Email alerts to billing admins and users is the default option and sends to everyone with billing admin or billing user roles on the target account. Email alerts to project owners is available only when the budget is scoped to a single project and sends to every Project Owner on that project. To opt out of the default billing-account emails, the checkbox must be cleared.
Custom email recipients use Cloud Monitoring notification channels for people who do not hold billing roles, such as project managers or developers. Only Email type channels are supported, and up to five email channels can be linked to one budget. The channel must be created in Cloud Monitoring first, then linked to the budget:
Automated responses use a Pub/Sub topic connected to the budget, with data flowing from the budget to the topic multiple times per day with current status. A subscriber can forward the message to Slack or run a cost-control task such as disabling billing on a project that exceeds its budget. If the Pub/Sub message must include alertThresholdExceeded and forecastThresholdExceeded, the budget needs at least one threshold rule. When threshold rules exist, at least one email option must stay enabled, so removing all threshold rules is the way to send only programmatic notifications without email.
Continue with this study guide: Establishing billing budgets and alerts
Cloud Billing 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. The three exports differ in granularity, so the level of detail in the cost question is the decision rule for which export to enable.
Standard usage cost data is the base-level export for invoice totals, cost trends, and project-level review. Standard usage cost data includes usage and cost estimates that support queries such as total costs per invoice, details by cost type per invoice month, and costs and credits by project. Detailed usage cost data is a superset of standard data with additional fields for granular, resource-level analysis. Detailed data contains everything in the standard export plus fields that identify the specific resource that generated usage, such as a virtual machine or SSD, and labels flow with resources so costs can be grouped by label key and value or broken down for Google Kubernetes Engine (GKE) clusters.
Pricing data 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.
| 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 |
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 defines who can turn on billing export and where the exported data can live. Data flows from the Cloud Billing account to tables inside a BigQuery dataset you specify, where it can be queried for 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 house the financial data.
Required permissions control who can enable the flow of financial data because exported billing data is sensitive. IAM ownership is required on both the source and the destination, shown as the IAM Owner role 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 with resourcemanager.projects.create permission. Only trusted administrators with account-level access can configure the destination and turn on export.
Preparing the destination creates the secure container that will receive billing data before export is enabled. The destination dataset lives inside a Google Cloud project 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. BigQuery requires the dataset to exist before Cloud Billing can write to it.
Destination rules also determine whether export will succeed. 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.
Turning on export 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, and the same dataset can hold standard usage cost data, detailed usage cost data, and pricing data. Data flows from the Cloud Billing account to the BigQuery dataset automatically throughout the day, then from BigQuery to analysis, reporting, and visualization tools.
Timing is critical because export only sends data forward from the time it is enabled and does not backfill history. Enable export at the same time you create each Cloud Billing account and before the project receives customer traffic, because data from before export was enabled will never appear in BigQuery. This forward-only behavior is why early setup keeps a complete dataset for invoice reconciliation and trend analysis.
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, runs a query that sums costs, and checks that expected projects, labels, and time ranges appear. Successful results mean the automated transfer 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.Continue with this study guide: Setting up billing exports
Linking a Google Cloud project to a Cloud Billing account requires create permissions on both resources at the same time. The caller needs billing.resourceAssociations.create on the billing account, held by Billing Account User and Billing Account Administrator, and resourcemanager.projects.createBillingAssignment on the project, held by Project Billing Manager and Project Owner. Unlocking or unlinking the same link is different because adequate delete permission on either side is sufficient.
Use standard usage cost data when you need invoice totals, cost trends, or project-level costs and credits, and use detailed usage cost data when you need to attribute cost to a specific resource, label, or Google Kubernetes Engine (GKE) cluster. Detailed usage cost data is a superset of standard data that contains everything in the standard export plus additional fields that identify the specific resource that generated usage, such as a virtual machine or SSD. Pricing data is separate because it provides list prices for specific stock keeping units (SKUs) that can be joined with detailed usage cost data to compare billed cost against list price.
Actual spend measures costs already incurred in the current budget period and is subject to billing reporting delay, while forecasted spend measures the projected total cost by the end of the calendar period and cannot be used with a custom time range. A budget sets a planned spend amount and threshold rules define a percentage of that amount, so when actual or forecasted spend crosses the percentage the budget triggers an alert to configured recipients. Because of reporting delay it is recommended to set the budget amount below available funds, and alerts-only budgets only inform and never automatically cap usage or stop spending.
Last updated