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.

• ✗

  Google Kubernetes Engine (GKE)

  Why it's wrong here

  Google Kubernetes Engine (GKE) provides a managed Kubernetes cluster, but it runs on a node pool of virtual machines that must remain active to support the control plane and system components. While the Horizontal Pod Autoscaler can scale Pods to zero, that would leave no endpoint to receive traffic, and the underlying nodes still incur per-second costs unless you manually detach them. GKE does not automatically scale the cluster to zero nodes; it requires you to manage node pools, cluster networking, and version upgrades, adding operational overhead. For a simple containerized web app, GKE's infrastructure management and non-zero minimum cost make it unnecessary and less cost-effective than a serverless alternative.

• ✗

  Compute Engine

  Why it's wrong here

  Compute Engine offers raw virtual machines that run continuously until you stop or delete them, and any autoscaling you configure via managed instance groups must maintain at least one running VM to serve requests. You are responsible for installing the container runtime, setting up Docker, and handling OS patches and security updates, which is complexity you don't want for a standard web app. Because the VM is always on, you pay for vCPU, memory, and disk even when there are no incoming requests, and there is no built-in mechanism to scale to zero while keeping the service available. This makes Compute Engine a poor fit for a containerized web app that needs cost-effective, automatic scaling; it's better suited for predictable, always-on workloads.

• ✓

  Cloud Run

  Why this is correct

  Cloud Run is a fully managed, serverless compute platform that executes stateless containers in response to HTTP requests. It automatically scales instances from zero up to handle traffic spikes and back down to zero when idle, so you pay only for the CPU and memory consumed during request processing—with no charge for idle-time zero-instance periods. Because Cloud Run abstracts away all infrastructure, you don't need to manage clusters, nodes, or virtual machines; you simply deploy a container image and let the service handle scaling, availability, and load balancing. This makes Cloud Run the ideal choice for a containerized web application with variable or intermittent traffic, providing minimal operational overhead and granular per-request billing.

• ✗

  App Engine Flexible Environment

  Why it's wrong here

  App Engine Flexible Environment does allow you to deploy Docker containers, but unlike App Engine Standard, it runs each instance inside a virtual machine that must stay resident to receive traffic. The environment cannot scale down to zero instances because it needs at least one VM to accept requests, which means you incur continuous costs even during periods of no usage. You also need to configure the VM to handle container health checks and scaling parameters, and you inherit the constraints of a fully managed PaaS (like limiting background thread access) while still paying for a dedicated VM. It's less cost-efficient than Cloud Run for a containerized web app that experiences intermittent traffic, and it lacks the simplicity of a truly serverless model.

Go deeper

Related to this question