Study guide
3.4 Billing Budgets and Alerts
Google Cloud Associate Cloud Engineer ACE
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Exam Overview
1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan
2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity
2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups
3 Chapter 3: APIs, Quotas & Billing Configuration
3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts
4 Chapter 4: Planning Compute & Storage Resources
4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types
5 Chapter 5: Planning Network Resources
5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard
6 Chapter 6: Deploying Compute Engine Workloads
6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration
7 Chapter 7: Deploying Google Kubernetes Engine Workloads
7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE
8 Chapter 8: Deploying Serverless & Event-Driven Applications
8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc
9 Chapter 9: Deploying Data Solutions
9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud
10 Chapter 10: Deploying Networking Resources & Infrastructure as Code
10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm
11 Chapter 11: Managing Compute Engine & GKE in Production
11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE
12 Chapter 12: Managing Cloud Run, Storage & Database Operations
12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)
13 Chapter 13: Networking Operations, Monitoring & Logging
13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs
14 Chapter 14: IAM Policies & Role Types
14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles
15 Chapter 15: Service Accounts & Security Configuration
15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials
16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy
16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist
3.4 Billing Budgets and Alerts
Key Takeaways Explain This Topic AI
Default budget alert thresholds are 50%, 90%, and 100% of actual spend, with up to 5 threshold rules and optional forecasted-spend alerts per budget.
Budgets can scope to an entire billing account or be filtered to specific projects, services, or labels.
A budget alert is a notification only - it never automatically stops spending or disables resources by itself.
Automated cost control requires custom automation: a Pub/Sub topic attached to the budget, consumed by a Cloud Function that calls the Cloud Billing API to disable billing.
Pub/Sub budget notifications are sent multiple times per day regardless of threshold state, a higher cadence than threshold-only email alerts.
Last updated: July 2026
Billing Budgets and Alerts
Quick Answer: A budget is a spending target you define for a billing account or a filtered subset of it; alerts are the notifications triggered once actual (or forecasted) spend crosses configurable percentage thresholds of that budget — defaulting to 50%, 90%, and 100% . The critical exam fact: a budget alert by itself never stops spending. It only notifies. Automated shutoff requires you to build it, typically with Pub/Sub and a Cloud Function.
Why This Matters on the Exam
"Establishing billing budgets and alerts" is a named bullet in the official ACE exam guide (Section 1.2), and it is tested with a recurring trap: candidates assume budgets behave like a hard spending cap (some other clouds' "budget actions" do this), and pick an answer implying automatic shutdown when the real answer is "configure a notification" or "you must build the automation yourself."
Where Budgets Are Configured
Budgets and their alert rules are created and managed entirely in the Cloud Billing console (Billing → Budgets & alerts) — the same console-only pattern as billing exports (Section 3.3). There is no dedicated gcloud budgets surface for day-to-day budget creation in the console workflow the exam tests; automation instead goes through the Cloud Billing Budget API .
Budget Scope
A budget can apply to:
An entire billing account (all linked projects, all services) — the simplest, broadest scope.
A filtered subset : specific projects, specific products/services, or specific labels (e.g., only the env:production label).
A specified amount you type in, last month's spend , or a custom amount synced from an external source via the API.
Alert Thresholds
Threshold type Default rules Customizable?
Actual spend Alerts fire at 50%, 90%, and 100% of budget Yes — up to 5 threshold rules per budget
Forecasted spend Optional — alerts when Google predicts spend will exceed a threshold by the end of the period, even if actual spend hasn't gotten there yet Yes, added alongside actual-spend rules
By default, alert emails go to Billing Account Administrators and Users (the same roles from Section 3.3) — you can add more recipients as monitoring notification channels.
Programmatic Notifications via Pub/Sub
For automation, you connect a Pub/Sub topic to the budget. Key distinction the exam likes to probe:
Email alerts fire only when a configured threshold is actually crossed.
Pub/Sub messages are published multiple times per day regardless of threshold state , each containing the current budget status ( budgetDisplayName , costAmount , budgetAmount , and boolean fields like alertThresholdExceeded / forecastThresholdExceeded ).
This higher-frequency, structured feed is what makes Pub/Sub the foundation for automated responses — for example, a Cloud Function subscribed to the topic that checks costAmount against budgetAmount and, if spend has hit 100%, calls the Cloud Billing API to disable billing on the project (which stops billable resources) or sends a Slack alert to an on-call channel.
The Core Trap: Budgets Do Not Enforce Spending Caps
This is the single most exam-relevant fact in this section: creating a budget and alert rules does nothing to stop resource creation or usage. Nothing is throttled, paused, or blocked automatically. If a scenario says "the team wants spending to be hard-capped at $5,000/month with no possibility of overage," the only correct architecture is the full Pub/Sub + Cloud Function (+ Cloud Billing API to disable billing) pattern — not "just create a budget." If the scenario only says "the team wants to be notified " when spend crosses a threshold, a plain budget with default alert thresholds is sufficient and the simpler, correct answer.
Exam Scenario
A startup's finance lead is worried about a runaway bill from an accidentally-oversized Compute Engine deployment and wants automatic action taken, not just an email, the moment total monthly spend reaches 100% of a $2,000 budget. The correct design: create the budget with a 100% actual-spend threshold, attach a Pub/Sub topic to the budget's programmatic notifications, and deploy a Cloud Function triggered by that topic that calls the Cloud Billing API to disable billing (or another guardrail action) once costAmount reaches budgetAmount — a budget alert alone, sent only by email, would not meet the "automatic action" requirement.
Common Traps
Picking "the budget will automatically shut down the project" as an answer — budgets are observational unless you build the automation.
Forgetting that Pub/Sub budget notifications arrive multiple times a day regardless of thresholds, which is different cadence from the threshold-based email alerts.
Missing that budgets can be scoped to labels , not just whole projects — useful for tracking one environment or team within a shared billing account.
Assuming a maximum of 3 thresholds (matching the 50/90/100 defaults) — you can actually configure up to 5 threshold rules per budget.
Key Takeaways
Default budget alert thresholds are 50%, 90%, and 100% of actual spend, with up to 5 thresholds and optional forecasted-spend alerts configurable per budget.
Budgets and billing exports are both configured in the Cloud Billing console , not via a dedicated gcloud command.
Pub/Sub budget notifications are sent multiple times daily regardless of threshold crossing — richer and more frequent than the threshold-only email alerts.
A budget alert is a notification, not an enforcement mechanism — hard spending caps require custom automation (Pub/Sub → Cloud Function → Cloud Billing API).