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.

• ✗

  Committed use discounts

  Why it's wrong here

  Committed use discounts (CUDs) lower the effective cost of resources in exchange for a 1- or 3-year spend commitment, so they only change the financial calculation on the bill. They do not emit spending alerts, nor do they provide any granular breakdown by project or service. Thus, while CUDs reduce total cost, they are unrelated to the alerting and analysis mechanisms the company needs.

• ✓

  Labels on resources

  Why this is correct

  Labels are key-value metadata attached to GCP resources, such as 'team' or 'environment', and they are the primary mechanism for sorting and grouping costs within an exported billing dataset. When combined with BigQuery billing export, labels let you slice costs by project, service, team, or any custom dimension, enabling exact repartition of spend. They are the correct tool because they make cost data attributable and queryable.

• ✗

  Active Assist idle resource recommendations

  Why it's wrong here

  Active Assist, including the idle resource recommender, uses machine learning to detect underutilized virtual machines or other resources and suggest downsizing or deletion. It is a cost-optimization advisory service, not a real-time alerting system or a cost-analysis dataset. These recommendations help reduce waste over time but do not provide the spending alarms or detailed spend breakdowns required for the company's goal.

• ✓

  Cloud Billing budgets

  Why this is correct

  Cloud Billing budgets let you set a spending threshold and receive alerts when actual or forecasted cost exceeds defined percentages (e.g., 50%, 90%, 100%). Alerts can be delivered through Cloud Monitoring notification channels, email, or Pub/Sub, making them effective for proactive overrun detection. However, budgets only trigger notifications; they do not contain detailed per-resource cost data needed for analytical reporting.

• ✓

  Billing export to BigQuery

  Why this is correct

  Billing export to BigQuery automatically sends daily detailed usage and cost logs to a BigQuery dataset, including resource metadata, labels, and pricing details. This export turns the raw billing information into queryable tables, allowing you to run custom SQL for historical trends, per-service cost, or label-based rollups. It is the backbone for any in-depth, self-serve cost analysis, though it does not itself generate alerts.

Go deeper

Related to this question