Billing, Budgets & Quotas
Google ACE ACE · Setting up a cloud solution environment
Billing accounts: the money side of a project
A billing account is the payment instrument for Google Cloud usage. It holds the payment method, the billing address, and the account settings, and it is linked to one or more projects. Every project that uses billable services must be linked to exactly one billing account; a project with no billing account can only use free-tier services. One billing account can pay for many projects, which is how most companies organize spending: a single company billing account linked to all production projects, for example, with a separate account for a subsidiary that needs its own invoicing. Billing accounts are managed in the console under Billing, and access to them is controlled by IAM roles such as Billing Account Administrator and Billing Account User — roles that exist specifically so finance staff can manage money without having access to the technical resources.
There are two kinds of billing account. A self-serve (online) account is the default: you pay by credit or debit card, and Google charges automatically. An invoiced (offline) account is for larger customers who pay by invoice on monthly terms; it requires an application and approval from Google. The exam rarely goes deep on invoicing, but you should know the distinction exists. What the exam does test is the link between projects and billing accounts: creating a billing account, linking a project to it, and unlinking a project (which stops all billable services in that project — VMs keep running until the end of the billing cycle in some cases, but the key point is that unlinking disables billable usage). A project can be moved from one billing account to another, which is useful when a project changes cost center.
Budgets and alerts
A budget in Google Cloud is a spending threshold with alert rules attached. You set a budget amount for a billing account (or filtered to specific projects, services, or labels), and you define alert thresholds — for example, email the finance team at 50%, 90%, and 100% of the budget. You can also trigger a Pub/Sub notification at a threshold, which lets you automate a response such as posting to a Slack channel or even shutting down resources through a Cloud Function. The critical exam fact is that a budget does not stop spending by itself. It only alerts. Many candidates assume reaching 100% of a budget caps the bill; it does not. If you want spending to actually stop, you must build automation that reacts to the budget alert, typically with Pub/Sub and Cloud Functions, or disable billing on the project manually.
Budgets can be scoped in useful ways. A budget on the whole billing account watches total company spend; a budget filtered to one project watches that project's spend; a budget filtered by label watches a team's or an application's spend across projects. Labels are the key to the last pattern: apply consistent labels (such as team: checkout or env: prod) to resources, and budgets and billing exports can then report costs by label. Forecasting is also built in: the console shows projected spend against the budget based on current usage trends, so an alert can fire before the money is actually spent.
Billing exports
Billing export sends detailed usage and cost data out of the billing system so it can be analyzed elsewhere. The standard export goes to BigQuery, where each day's (or each hour's, if detailed usage cost export is enabled) charges land in a dataset you control, and you can query them with SQL — cost by project, by service, by label, by SKU. There is also an export to a Cloud Storage bucket as CSV or JSON files, which suits archival or ingestion into third-party tools. Billing export is configured per billing account, not per project, and it only starts from the moment you enable it — it does not backfill historical data. The exam likes the BigQuery export because it is the foundation for serious cost analysis: if a question asks how to answer "which team spent the most on BigQuery last quarter", the answer is billing export to BigQuery plus a query, not the console's cost table.
Quotas and cost controls
Quotas were introduced in the previous guide as limits on resource usage, and they have a billing dimension too: many quotas are higher once a billing account is linked, and some services cannot be used at all without billing. A quota increase request is reviewed by Google and can take time, so the exam expects you to plan quota checks into project setup rather than discovering a limit during a deployment. Note the distinction between quotas and budgets: a quota is a hard limit enforced by Google on resource quantity (it blocks creation), while a budget is a soft spending threshold that only alerts. Both are cost controls, but they work in opposite ways — one prevents usage, the other reports on it.
Two more billing concepts round out this topic. Committed use discounts give significant price reductions (up to 57% for most Compute Engine machine types, depending on the term) in exchange for committing to a level of usage for one or three years — they are a planning tool, not something the ACE exam tests in detail, but knowing they exist helps with cost questions. Sustained use discounts apply automatically to Compute Engine: the more a VM runs in a month, the lower its effective hourly price, with no commitment needed. Neither replaces budgets: discounts reduce the unit price, budgets watch the total.
Common billing exam scenarios
Billing questions on the ACE exam tend to follow a few patterns. One is the surprise bill: a developer leaves resources running, and the question asks what should have been set up — the answer is a budget with alerts, often combined with billing export for analysis. Another is the shared account: several teams share one billing account and finance needs per-team costs — the answer is labels plus billing export to BigQuery. A third is the blocked deployment: a service refuses to start because billing is not enabled on the project — the answer is to link the project to a billing account. In each case, the exam rewards knowing which tool does which job: budgets alert, exports analyze, labels attribute, and billing accounts pay.
Exam traps to watch for
- Assuming a budget stops spending: budgets only alert. Stopping spending requires automation (Pub/Sub + Cloud Functions) or manual action.
- Confusing billing export with budgets: export sends detailed cost data to BigQuery or Cloud Storage for analysis; budgets watch thresholds.
- Forgetting that billing export does not backfill — it only captures data from the moment it is enabled.
- Linking a project to more than one billing account: a project has exactly one billing account at a time.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A finance team wants to be notified by email when a project's spending reaches 50%, 90%, and 100% of $5,000 per month. What should they configure?
Explanation: Budgets are exactly this tool: a spending threshold with alert rules at chosen percentages, and they can be filtered to a single project. A quota increase changes resource limits, not spending alerts. Billing export sends cost data elsewhere for analysis but does not send threshold alerts. Organization policies restrict what resources may do; they do not monitor spending.
Exam objective: ACE exam guide 1.2: Managing billing configuration — establishing billing budgets and alerts
Q2.A company's monthly bill was far higher than expected. The finance team wants to analyze the charges in detail — cost by project, by service, and by label — using SQL queries. What should they set up?
Explanation: Billing export to BigQuery loads detailed daily (or hourly) cost data into a dataset where it can be queried with SQL by project, service, SKU, and label. A budget with Pub/Sub sends threshold notifications but does not provide queryable history. Enabling the Billing API does not export cost data. An invoice PDF is a summary document, not a queryable dataset.
Exam objective: ACE exam guide 1.2: Managing billing configuration — setting up billing exports
Q3.A developer creates a new project and tries to launch a Compute Engine VM, but the operation fails because billing is not enabled. What is the correct fix?
Explanation: A project must be linked to a billing account before it can use billable services such as Compute Engine VMs, and the error message names the problem directly. A budget only monitors spending and does not enable billing. A quota increase changes resource limits, not billing status. Enabling the Compute Engine API is necessary but not sufficient — the API can be enabled while billing is still missing.
Exam objective: ACE exam guide 1.2: Managing billing configuration — linking projects to a billing account
Q4.A team lead wants spending to automatically stop when a project reaches its monthly budget, so the bill can never exceed the limit. What should you tell them?
Explanation: A budget is an alerting mechanism only — reaching 100% sends notifications but does not cap spending. Automatic enforcement requires automation triggered by the budget alert, typically a Pub/Sub notification that invokes a Cloud Function to disable billing or shut down resources. Quotas limit resource quantities, not spending, and organization policies cannot react to spending thresholds.
Exam objective: ACE exam guide 1.2: Managing billing configuration — establishing billing budgets and alerts
Q5.A company has one billing account shared by five teams. Finance needs a monthly report of each team's spending. The teams already label all their resources with a team label. What is the best approach?
Explanation: Billing export to BigQuery captures label data with every charge, so a single query can produce accurate per-team costs without restructuring billing. Splitting into five billing accounts would work but is disruptive and unnecessary when labels already exist. Budgets track thresholds, not actual per-team totals. Manual estimates from the console are imprecise and do not scale.
Exam objective: ACE exam guide 1.2: Managing billing configuration — setting up billing exports
Q6.Which statement about billing accounts is correct?
Explanation: One billing account pays for many projects — that is the normal enterprise pattern. A project is linked to exactly one billing account at a time. Billing export only captures data from the moment it is enabled; it does not backfill history. A project without a billing account cannot use billable services at all, beyond the free tier.
Exam objective: ACE exam guide 1.2: Managing billing configuration — creating billing accounts and linking projects
Q7.A startup's developers keep forgetting to shut down test VMs, and costs are climbing. The CTO wants an automated warning when any project's daily spend spikes, plus the ability to investigate which service caused the spike. Which combination should you recommend?
Explanation: Budgets provide the alerting (thresholds on spend, optionally with Pub/Sub for automation), and billing export to BigQuery provides the detailed, queryable data needed to identify which service caused a spike. A quota increase would make the problem worse by allowing more resources. Export alone gives data but no alerting. A second billing account separates the bill but neither alerts nor analyzes.
Exam objective: ACE exam guide 1.2: Managing billing configuration — establishing billing budgets and alerts; setting up billing exports
Q8.A project is being transferred from the marketing department to the engineering department, and engineering has its own billing account. What must happen for engineering to pay for the project's usage going forward?
Explanation: A project can be moved between billing accounts by unlinking it from one and linking it to the other — the project and its resources are unaffected. Deleting and recreating the project would destroy all its resources unnecessarily. A budget only monitors spending; it does not change who pays. Project IDs are permanent and have nothing to do with billing.
Exam objective: ACE exam guide 1.2: Managing billing configuration — linking projects to a billing account