GCP ACE Practice / Study guide / Topics / Billing, Pricing & Cost Management
Billing, Pricing & Cost Management
What actually gets tested on the Google Cloud Associate Cloud Engineer exam,
the traps to know, and 6 free sample questions with full explanations.
A project links to exactly one billing account at a time, and changing that link needs both Project Billing Manager on the project and Billing Account User on the account — a two-sided permission the exam likes to test directly. One billing account can fund many projects, which is the normal setup for an organization: central finance owns billing, individual teams own their projects.
The single most-repeated trap in this topic is that a budget alert doesn't cap spending. Budgets are set on a billing account with percentage thresholds that trigger email notifications to billing admins/users, and optionally a Pub/Sub message you could wire up to automate a response yourself — but nothing about a budget alert, by itself, stops a service from running or a bill from growing. If a question wants spend actually capped, the answer involves quotas, a programmed response to the Pub/Sub notification, or simply not provisioning more than intended in the first place.
On discounts, keep sustained use and committed use straight: sustained use discounts apply automatically to steady month-long Compute Engine usage with no commitment required, while committed use discounts need a 1- or 3-year up-front commitment in exchange for a deeper discount. For visibility into what's actually being spent, Billing export to BigQuery writes detailed line-item usage and cost data (including labels) somewhere finance can run SQL against it or connect a BI tool like Looker Studio.
Exam tips for this topic
- A budget alert is a notification, not a spending cap — nothing about it stops a service or reduces the bill by itself.
- Sustained use discounts are automatic for steady month-long usage; committed use discounts require a 1- or 3-year up-front commitment for a deeper rate. Don't swap these.
- Moving a project to a different billing account needs Billing Account User on the account AND Project Billing Manager on the project — one alone isn't enough.
Sample questions — Billing, Pricing & Cost Management
These 6 questions are drawn from our full bank of 658 to show the style and
depth you'll get in the app. Each comes with the full explanation you'd see after answering
in a real practice session.
Billing
A project's resources keep running but you want a different department to pay for them. What should you do?
- Link the project to the other department's billing accountCorrect
- Export the project's resources to a new project owned by the other department
- Create a new billing budget in the other department's name
- Transfer the organization node to the other department
Why: A project is linked to exactly one billing account at a time, and changing that link (requires Project Billing Manager on the project plus Billing Account User on the target account, or Billing Account Administrator) redirects all future charges without touching any resources. Migrating resources or reorganizing the hierarchy is unnecessary, and budgets only monitor spend — they don't change who pays.
Pricing
Which pricing tool answers 'what will this architecture cost per month' during design?
- Google Cloud Pricing CalculatorCorrect
- The billing export dataset in BigQuery
- The Quotas page under IAM & Admin
- Cloud Trace's cost breakdown view
Why: The Pricing Calculator models planned usage (VMs, disks, storage, egress...) into a monthly estimate you can share. Billing export analyzes actual past spend; quotas and Trace are unrelated to cost estimation.
Quotas
Your team hit the CPU quota in a region and cannot create more VMs. What should you do?
- Request a quota increase from the Quotas page in IAM & Admin (or via gcloud)Correct
- Create a new billing account and link the project to it to reset the regional limits
- Disable and re-enable the Compute Engine API to refresh the project's quota allocation
- Switch the new VMs to preemptible instances, which are exempt from CPU quota
Why: Quotas are per-project (often per-region) limits that you can view and request increases for on the Quotas page; increases are reviewed by Google. Billing accounts and API enablement don't change quota, and Spot/preemptible VMs consume the same CPU quota family (a separate preemptible quota can exist, but it doesn't 'bypass' limits).
Billing
You want to be notified when a project's monthly spend reaches 50%, 90%, and 100% of $1,000. What should you configure?
- A budget on the billing account with threshold alert rules at 50%, 90%, and 100%Correct
- A billing export to BigQuery with a scheduled query that emails the finance team daily
- A quota limit of $1,000 configured on each of the project's billable services
- A Cloud Monitoring alerting policy with an uptime check on the billing account
Why: Budgets are set on a billing account (scoped to one or more projects) with percentage thresholds that trigger email notifications, and optionally Pub/Sub messages for programmatic action. Quotas limit API/resource usage, not dollar amounts; billing export enables analysis but has no built-in alerting; uptime checks monitor endpoints.
Pricing
Your steady-state web tier will run 24/7 for years on N2 VMs. Beyond sustained use discounts, what should you evaluate to cut compute cost?
- Committed use discounts (1- or 3-year commitments)Correct
- Moving the customer-facing web tier onto Spot VMs
- Switching the VMs to the Premium network tier
- Adding more cost-allocation labels to the VMs
Why: Predictable, always-on usage is the CUD sweet spot — commitments yield larger discounts than SUD. Spot is inappropriate for availability-sensitive serving; network tier and labels don't reduce compute spend.
Quotas
What is the difference between rate quotas and allocation quotas?
- Rate quotas reset over a time window, like API requests per day; allocation quotas cap resources that exist at once, like VM countCorrect
- Rate quotas apply only to billing spend, while allocation quotas govern API request volume and reset monthly
- Allocation quotas reset automatically every hour, while rate quotas never reset and require a support case to raise
- They are two names for the same mechanism; the console simply shows them on two different pages
Why: Rate quotas limit how often you can do something and replenish over time; allocation quotas limit how much you can hold at once and free up only when resources are deleted. Understanding which one you hit determines whether waiting or deleting/requesting an increase is the fix.
Practice this for real
The app has dozens more questions on this and every other topic, with instant scoring,
spaced repetition of what you get wrong, and progress tracking across sessions.
Start practicing →
This topic shows up in
Other topics