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 is a suite of Google Cloud tools that analyze existing, already-deployed resources to provide optimization recommendations, such as right-sizing over-provisioned VMs or identifying idle projects. Because these recommendations are derived from historical telemetry and usage patterns of live workloads, they do not provide a forward-looking monthly cost estimate for a new service that has not yet been built. Therefore, Active Assist is unsuitable for pre-deployment cost estimation.

• ✓

  Google Cloud Pricing Calculator

  Why this is correct

  The Google Cloud Pricing Calculator is the correct tool for estimating monthly costs before deployment because it accepts user-defined resource specifications, including machine type, region, persistent disk size, estimated usage hours, and committed use discount terms. It references Google Cloud's current public SKU pricing to generate a detailed, line-item cost estimate for a proposed workload, enabling architects to model multi-component architectures and assess the financial impact of configuration choices before committing to them.

• ✗

  Budget alerts

  Why it's wrong here

  Budget alerts in Google Cloud are configured against a budget you set, and they send notifications when actual incurred spend reaches a defined threshold (for example, 50%, 90%, or 100% of the budget). They rely on real-time billing data from resources that are already running, so they serve as a reactive monitoring control rather than a forecasting tool. Without a pre-existing deployed workload, there is no spend to track, making budget alerts incapable of predicting the monthly cost of a proposed service.

• ✗

  Cost Management dashboard

  Why it's wrong here

  The Cost Management dashboard in the Google Cloud console presents after-the-fact billing information, including cost breakdowns by project, service, region, and labels, but it only reflects charges that have already been incurred by the organization. Since the data populates from actual usage and invoices, it provides no ability to input hypothetical resource configurations or to project future spending for a service that has not yet been deployed. It is designed for retrospective cost analysis and spend tracking, not for pre-deployment cost estimation.

Go deeper

Related to this question