Cloud Digital Leader Scaling with Google Cloud operations 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.

• ✗

  Cloud Monitoring — set alerts for low CPU utilization.

  Why it's wrong here

  Cloud Monitoring can absolutely alert you when a VM's CPU utilization drops below a threshold, but that is where its capability ends. It gives you the raw telemetry and lets you define alerting policies, yet it does not analyze historical utilization patterns across multiple resources, nor does it correlate memory pressure or network traffic to determine whether a smaller machine type would be safe. Most importantly, Cloud Monitoring will not generate a recommendation like 'change from e2-standard-8 to e2-standard-4 to save X dollars per month.' It is a monitoring and observability tool, not a cost-optimization advisor, so relying on it here would leave you with alerts to triage but no specific resizing guidance.

• ✓

  Active Assist Recommender — ML-based VM rightsizing recommendations.

  Why this is correct

  Active Assist Recommender is the correct service because it uses machine learning trained on near-real-time utilization metrics from Compute Engine, including CPU, memory, network, and disk I/O, to generate specific rightsizing recommendations for each VM. For example, it may suggest moving from n2-standard-8 to n2-standard-4 based on sustained low usage, and it also provides an estimated monthly savings and a confidence score for every recommendation. These recommendations are actionable directly from the console or via the Recommender API, allowing you to apply the machine type change in one click or through infrastructure-as-code. This is precisely the targeted, data-driven guidance the scenario asks for—not just raw metrics or aggregate alerts.

• ✗

  Cloud Asset Inventory — lists all VMs and their configurations.

  Why it's wrong here

  Cloud Asset Inventory provides a complete, immutable snapshot of your cloud resources—all VM instances, their machine types, zones, labels, and network configurations—which is great for security, compliance, and change tracking. However, it does not collect or retain time-series utilization data, and it has no ML-based analysis engine to identify overprovisioned instances. You could query it to find every VM running an n2-standard-8, but you would have no idea which of those VMs are actually using 10% of their CPU and could be safely downgraded. It describes your resource estate but cannot tell you what to change to optimize cost, making it useful for asset discovery but not for generating rightsizing recommendations.

• ✗

  Cloud Billing budgets — set spending limits to prevent overspend.

  Why it's wrong here

  Cloud Billing budgets are a cost-governance tool that monitors aggregate spending against predefined thresholds and sends alerts when you approach a set limit. While they can prevent bill shock, they operate at the billing-account or project level and do not analyze individual VM utilization. A budget will not tell you that a specific n2-standard-8 instance is idle or that its workload fits in an n2-standard-4, nor will it project the savings from such a change. Budgets enforce financial boundaries, not compute optimization decisions.

Go deeper

Related to this question