Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Google Kubernetes Engine (GKE)

  Why it's wrong here

  Google Kubernetes Engine (GKE) is a managed Kubernetes service that abstracts container orchestration but still requires an underlying cluster of node VMs. Even with cluster autoscaling, the node pools have a minimum size that cannot drop to zero, and you pay for the control plane's management overhead and the node's compute, memory, and storage capacity while idle. Therefore, GKE does not offer the pay-per-use, scale-to-zero model needed for a low-traffic startup's cost concer.

• ✗

  App Engine Standard Environment

  Why it's wrong here

  The App Engine Standard environment is a fully managed platform that automatically scales instances to zero, but it does not support running arbitrary containers. Instead, it requires applications to be written in specific supported language runtimes and restricts the execution environment to those sandboxed runtimes, meaning a custom containerized web application cannot be deployed there. To run a container while retaining scale-to-zero, you would need Cloud Run or App Engine Flexible, not Standard.

• ✓

  Cloud Run

  Why this is correct

  Cloud Run is a fully managed, serverless compute platform that executes stateless HTTP-driven containers on top of the Knative serving layer. It dynamically scales containers from zero up to a maximum based on incoming requests, so you only pay for CPU, memory, and requests consumed during active processing, making it ideal for intermittent startup workloads. Because it abstracts the underlying machines and cluster, there is no idle infrastructure cost and no node management overhead.

• ✗

  Compute Engine with autoscaling

  Why it's wrong here

  Compute Engine instances with autoscaling use a managed instance group to add or remove VMs based on CPU utilization, load balancer traffic, or other metrics, but the minimum instance count cannot be set to zero. This means at least one VM is always running, incurring continuous cost for the full instance's CPU, memory, and disk even when the web application has no traffic. Additionally, each instance requires OS and application maintenance, and autoscaling reacts in tens of seconds to minutes, not the sub-second request-level scale of serverless.

Go deeper

Related to this question