Cloud Digital Leader Google Cloud Products and Services 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.

• ✗

  Compute Engine

  Why it's wrong here

  Compute Engine is an Infrastructure-as-a-Service offering that requires you to provision, configure, and manage virtual machine instances, including patching, networking, and capacity planning. Even when using managed instance groups with autoscaling, you must set a minimum instance count (typically 1) because a VM pool must exist to handle traffic, and you pay for each allocated vCPU and memory regardless of utilization, so it never scales to zero. Running containers on Compute Engine (e.g., via Container-Optimized OS) still forces you to manage the host VM lifecycle, making it a poor fit for a startup that wants to pay only for actual request processing.

• ✓

  Cloud Run

  Why this is correct

  Cloud Run is a fully managed, Knative-based serverless platform that executes stateless containers in a scale-to-zero model: when there are no incoming requests, it shuts down all instances and you pay nothing. Each request is billed in 100-millisecond increments of compute time plus a minimal per-request charge, and it automatically scales to handle variable traffic, including bursting to thousands of concurrent requests. It accepts any container image that uses an HTTP server, which directly matches the need to deploy a containerised web application without managing any underlying nodes or clusters.

• ✗

  Google Kubernetes Engine (GKE)

  Why it's wrong here

  Google Kubernetes Engine provides a managed Kubernetes control plane but delegates operational responsibility for worker nodes to you (or to Autopilot, which still provisions and bills for underlying nodes). A GKE cluster cannot scale to zero because system components such as kubelet, networking, and cluster add-ons must run on at least one node, meaning you incur continuous hourly node costs even for a single low-traffic service. While GKE offers fine-grained autoscaling and is excellent for complex microservices, it is overkill and more expensive for a startup that needs a simple containerised web app with ephemeral, event-driven traffic, and it does not provide per-request billing like serverless platforms.

• ✗

  App Engine Standard

  Why it's wrong here

  App Engine Standard is a PaaS that scales to zero automatically, but it constrains applications to specific language runtimes and declared dependencies—it does not accept arbitrary container images. You must write your application in Java, Python, Go, PHP, Node.js, or Ruby and use the provided runtime sandbox, which limits flexibility if your web application uses system libraries or native binaries. The newer App Engine Flexible environment supports custom containers, but it is not the Standard environment and it does not scale to zero, so it does not meet the 'containerised web app with variable traffic' requirement as cleanly as Cloud Run.

Go deeper

Related to this question