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.

• ✗

  Active Assist recommendations

  Why it's wrong here

  Active Assist recommendations are generated by analyzing existing Google Cloud resources, their usage patterns, and configuration telemetry to suggest optimizations like rightsizing, idle resource removal, or IAM policy changes. Because they rely on deployed infrastructure and historical metrics, they cannot be used to estimate the monthly cost of a hypothetical or yet-to-be-created workload. For a startup needing a pre-deployment cost projection, Active Assist is not applicable, as it only provides actionable insights for resources that already exist and are incurring charges.

• ✗

  Cost Management dashboard

  Why it's wrong here

  The Cost Management dashboard in the Google Cloud console presents actual incurred costs, budgets, and alerts based on billing data that has already been aggregated from real usage. It can also display forecasts, but those extrapolate from past spend trends rather than from a specific resource configuration you propose to run. Since the startup wants to estimate costs before deploying anything, the dashboard cannot provide a quote or estimate; it only reflects costs that have already been metered and billed.

• ✓

  Google Cloud Pricing Calculator

  Why this is correct

  The Google Cloud Pricing Calculator is the correct tool because it enables users to select specific Google Cloud products, configure their parameters (e.g., machine type, region, storage class, network egress), and immediately see a detailed monthly cost estimate. It also incorporates pricing tiers, custom machine types, and can account for committed use discounts or sole-tenant nodes, giving a flexible and reasonably accurate projection for a planned workload. This makes it ideal for a startup that needs to budget before any actual infrastructure is created, as it translates desired resource specifications into an estimated monthly bill.

• ✗

  Billing export to BigQuery

  Why it's wrong here

  Billing export to BigQuery is a feature that writes detailed usage and cost records from Google Cloud billing to a BigQuery dataset for subsequent analysis, reporting, and dashboarding. It operates on historical data that is generated after resources have been used, meaning it can only describe what you have already spent, not estimate what you might spend in the future. For a startup in the planning phase, this would be useless for estimating monthly costs, as no usage records exist yet for the unbuilt environment.

Go deeper

Related to this question