Cloud Billing Study Notes

Cloud Billing is the system that links your projects to a payment method, tracks charges, and gives you budgets, alerts, and exports to control spending. It separates who can pay and manage costs from who can build resources. Billing questions on the ACE exam focus on account structure, roles, and stopping runaway spend safely.

Key facts

• A Cloud Billing account defines who pays for Google Cloud usage, is linked to a payments profile, and can be shared across many projects and even across organizations.
• Every project that uses billable resources must be linked to exactly one active billing account, and a project with no linked account or a closed account cannot start billable services.
• There are two billing account types at the time of writing: self-serve accounts paid by card or bank debit, and invoiced accounts for eligible larger customers billed monthly.
• Billing roles are separate from project roles: Billing Account Administrator, Billing Account Costs Manager, Billing Account Viewer, and Project Billing Manager control different billing tasks.
• Budgets let you set a monthly, quarterly, or custom-period amount per billing account, project, folder, or service, and trigger email alerts at thresholds you define.
• Budget alerts notify billing admins and can also publish to Pub/Sub, which lets you automate responses such as sending alerts to a team channel or triggering functions.
• Billing data can be exported to BigQuery for detailed analysis and to Cloud Storage as files, with standard and detailed usage cost data available at different granularity.
• If a billing account is closed, projects linked to it stop working for billable services until they are linked to another valid billing account by an authorized user.
• Committed use discounts and sustained use discounts affect pricing automatically where applicable, but they are managed through billing and do not change how resources are created.

What the exam expects you to know

• The exam tests linking and unlinking projects from billing accounts and which billing role is required, especially the Project Billing Manager role on both project and account.
• Expect a scenario about unexpected spend where creating a budget with alerts is correct, but you must know budgets alone do not stop usage without automation.
• Questions often ask where to export billing data for custom reports and SQL analysis, and the expected answer is BigQuery billing export rather than the console alone.
• You should distinguish billing account administrators who manage payment and users from project owners who manage resources but may have no billing permissions at all.
• Scenarios may ask how to give finance visibility without giving them resource access, which points to Billing Account Viewer or Costs Manager on the billing account only.
• The exam may check that closing or disabling billing on a project stops billable resources, which is drastic and different from setting a budget threshold alert.

Cloud Billing vs Budgets in Cloud Billing vs Billing Export to BigQuery: when to use which

Use budgets when you need proactive notification and control points around a spending amount for a project, folder, or service. Budgets answer the question of how close am I to a limit and who should be told. Use billing export to BigQuery when you need detailed, queryable history to analyze cost by label, SKU, project, or time and to build dashboards. In practice you enable both: the export gives finance and engineers the data to understand spend, while budgets give timely warnings. If a scenario asks for alerts, choose budgets; if it asks for analysis or custom reporting, choose the export. See also the Budgets in Cloud Billing vs Billing Export to BigQuery notes.

Useful gcloud commands

gcloud billing accounts list
gcloud billing projects list --billing-account=ACCOUNT_ID
gcloud billing projects link PROJECT_ID --billing-account=ACCOUNT_ID
gcloud alpha billing budgets list --billing-account=ACCOUNT_ID

Common exam traps

• Trap: Assuming a budget automatically caps or stops spending. By default a budget only sends notifications; stopping resources requires extra automation through Pub/Sub and Cloud Functions or manual action.
• Trap: Giving someone Owner on a project to fix billing. Billing linkage needs specific billing roles, and broad Owner access violates least privilege for a simple billing task.
• Trap: Thinking each project needs its own billing account. One billing account normally serves many projects; separate accounts are used for distinct payers or legal entities.
• Trap: Confusing a Google payments profile with a Cloud Billing account. The payments profile holds payment methods and tax details, while the billing account links that profile to cloud projects.

Frequently asked questions

How do you stop charges quickly if a project is compromised?

Disable billing for the project or close the billing linkage if you have permission, understanding that this will stop billable services and may cause data loss if resources shut down. A budget alert alone will not stop the charges. For exam scenarios, disabling billing is the emergency brake, while budgets and alerts are the early warning system.

Who can link a project to a billing account?

You need permission on both sides: the Project Billing Manager role or Owner on the project, and Billing Account User or Administrator on the target billing account. Missing either side causes the link to fail. This two-sided requirement is a favorite exam detail because it explains why a project owner alone sometimes cannot fix billing.

What is the difference between standard and detailed billing export?

Standard export to BigQuery gives cost by project and service suitable for most reporting, while detailed export adds resource-level granularity for deeper analysis. Both are delivered automatically once enabled, but data is not retroactive before enablement. The exam expects you to enable export early if a scenario requires historical cost analysis later.

Study aid disclaimer: Cloud Cert Notes is an independent educational study aid. It is not affiliated with, endorsed by, or sponsored by Google, Microsoft, Amazon, Oracle, or Alibaba. Google Cloud, Associate Cloud Engineer, and Cloud Digital Leader are trademarks of Google LLC; all other certification names and product names are trademarks of their respective owners. Always confirm service details against the official provider documentation before sitting an exam.