Cloud Digital Leader How Google Cloud Resources Are Managed Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Enable billing export to BigQuery and set up a scheduled query

  Why it's wrong here

  Enabling billing export to BigQuery and creating a scheduled query is meant for deep historical analysis, not real-time alerting. The export pipeline typically delivers data on a periodic schedule (e.g., daily or hourly), and the scheduled query would need to poll the dataset to evaluate spend thresholds, introducing latency. Cloud Billing already provides native budget alerts that trigger in near real-time, making this approach both more complex and less timely. It also does not leverage Google Cloud's built-in forecast capabilities, which are essential for proactive cost management.

• ✓

  Select 'Forecasted spend' as the alert threshold type in the budget configuration

  Why this is correct

  Selecting 'Forecasted spend' as the alert threshold type is the correct native method for forecast-based alerts. In the Cloud Billing budget configuration, you define threshold rules that can apply to either actual spend or forecasted spend. When you choose 'Forecasted spend' and set a percentage (e.g., 90%), the alert fires when Google's forecasting model predicts that your end-of-month spend will exceed that threshold. This proactive approach uses machine learning on historical usage patterns, enabling you to act before an overrun occurs, rather than reacting after costs are already incurred.

• ✗

  Create a Cloud Function that checks current spend every hour

  Why it's wrong here

  Creating a Cloud Function to poll current spend every hour is an unnecessary and inferior alternative. Google Cloud budgets already have built-in alerting that can send notifications via email, Cloud Monitoring, and Pub/Sub without any custom code. Additionally, polling every hour only captures actual, already-incurred spend, so it cannot provide forecasted predictions of future costs. This approach introduces operational overhead, potential for missed alerts between polls, and is not event-driven; native budget alerts are near-real-time and support both actual and forecasted thresholds, making the Cloud Function redundant for this use case.

• ✗

  Use the Cost Management API to query forecast data

  Why it's wrong here

  Using the Cloud Billing Cost Management API to query forecast data is an alternative that requires significant custom infrastructure. The API can return cost and forecast information programmatically, but it does not have built-in alerting or notification mechanisms; you would need to write your own polling loop and dispatch logic to trigger alerts. Conversely, the Budgets UI and underlying budget configuration natively allow you to set 'Forecasted spend' thresholds, which automatically fire alerts to your chosen channels. Thus, the API is not required for this scenario and only introduces unnecessary complexity and maintenance overhead.

Go deeper

Related to this question