3.4 Billing Budgets and Alerts

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

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).