Google ACE Practice Question: Receive email notifications when your GCP…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Cloud Monitoring alerting policies on billing metrics.

  Why it's wrong here

  Cloud Monitoring alerting policies require a metric to alert on, but Cloud Monitoring does not expose billing spend as a standard metric in its metric system; billing cost data lives in Cloud Billing, not in Cloud Monitoring's resource metrics. To create such an alert you'd have to ingest billing data into Monitoring as custom metrics, which is an unsupported and convoluted workaround. Cloud Billing Budget is the native service designed to monitor and notify on spend, making monitoring policies the wrong tool for this requirement.

• ✓

  Cloud Billing Budget with alert thresholds at 50%, 80%, and 100%.

  Why this is correct

  Cloud Billing Budget is the purpose-built feature for monitoring spend: it lets you set a budget amount and define multiple percentage-based alert thresholds (50%, 80%, 100%) that trigger notifications when actual or forecasted costs cross each threshold. Alerts are delivered either to billing account contacts via email or programmatically through Pub/Sub, enabling immediate, low-cost monitoring without custom tooling. Importantly, the budget itself never stops spending; it only notifies you, which is exactly what the question asks for.

• ✗

  Set a project spending limit in the Cloud Console billing settings.

  Why it's wrong here

  GCP does not provide a native per-project spending limit that automatically stops cloud usage; the only built-in construct is a Cloud Billing Budget with alert thresholds, which notifies you but does not enforce a cap. The Cloud Console billing settings allow you to set the budget amount and thresholds, but the name 'spending limit' is misleading—there is no mechanism to stop services once the limit is reached. For automatic enforcement, you would need to build a custom automation (e.g., a Cloud Function triggered by Pub/Sub notifications) to shut down resources, which is beyond a simple console setting.

• ✗

  Enable billing export to BigQuery and create a scheduled query that sends alert emails.

  Why it's wrong here

  While exporting billing data to BigQuery is excellent for deep historical analysis and custom reporting, building a scheduled query to send alert emails requires you to design a query against exported billing tables, handle Cloud Scheduler, Pub/Sub, and a notification service, and manage updating credentials and scheduling windows. This approach adds significant operational complexity and introduces latency (exports happen periodically, typically every 5–6 hours), so it cannot provide timely threshold alerts as efficiently as Cloud Billing Budget, which is integrated and near-real-time.

Go deeper

Related to this question