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.

• ✗

  Create a budget alert in Cloud Monitoring with a metric threshold of 80%

  Why it's wrong here

  Cloud Monitoring alerting policies are designed for operational telemetry such as CPU utilization, latency, and error rates, not for financial thresholds. There is no native budget-alert rule type in Cloud Monitoring, and it cannot directly evaluate spend against a billing-account budget. Budget notifications must be created in the Billing section of Cloud Console, which is the service that owns spend tracking. Using Cloud Monitoring would require building a custom, indirect pipeline from billing exports, which is neither the intended nor supported approach for this requirement.

• ✓

  Set up a budget in the Billing section of Cloud Console, define the amount, and add alert thresholds at 80%

  Why this is correct

  Cloud Billing budgets, configured under the Billing section of Cloud Console, are the official service for monitoring spend against a defined amount. You set a budget amount and then add alert threshold rules, such as 80% of the budget, which trigger notifications when actual or forecasted spend crosses that threshold. These alerts are event-driven and can deliver email or Pub/Sub messages, enabling immediate reaction when spending approaches the limit. This directly satisfies the company's requirement to be notified when monthly spend reaches 80% of the planned amount.

• ✗

  Use the Google Cloud Pricing Calculator to set a spending limit

  Why it's wrong here

  The Google Cloud Pricing Calculator is a planning tool that estimates future costs based on user-selected services and configurations; it does not connect to live billing data. It cannot create a spending limit, enforce alerts, or monitor actual monthly spend, because it is entirely disconnected from the billing system. The calculator produces static estimates only, so it is incapable of generating notifications when a real budget threshold is exceeded. For proactive spend alerts, the company must use Cloud Billing budgets, not a cost-estimation utility.

• ✗

  Configure a Cloud Scheduler job to check billing data in BigQuery and send a notification

  Why it's wrong here

  Cloud Scheduler triggers jobs on a fixed schedule, not in response to real-time spending thresholds; the requirement demands an alert when a specific budget percentage is exceeded, which requires an event-driven trigger such as a budget alert rule. It is tempting because Cloud Scheduler can query BigQuery billing data and send notifications, making it suitable for periodic cost reports, but it cannot react to an instantaneous spending condition without a polling loop that introduces latency.

Go deeper

Related to this question