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.

• ✗

  App Engine Standard Environment

  Why it's wrong here

  App Engine Standard is a sandboxed PaaS that only supports a fixed set of runtimes (e.g., Java, Python, Go, Node.js, PHP, Ruby) and does not allow you to provide your own Docker image. Because your application is containerized, you need a platform that can run arbitrary containers with custom system libraries and dependencies, which App Engine Standard cannot do. It also enforces request timeouts and filesystem restrictions that make many real-world container workloads unsuitable, even though it can scale to zero.

• ✗

  Google Kubernetes Engine (GKE)

  Why it's wrong here

  GKE is a managed Kubernetes orchestrator that requires a node pool of VMs to schedule and run your containers. While the cluster autoscaler can add or remove nodes based on load, it cannot scale the cluster to zero when there is no traffic; you still need at least one node per node pool, so you keep paying for compute capacity even if your container is idle. Additionally, you are responsible for node maintenance, upgrades, and cluster control plane costs, which adds operational overhead and makes GKE heavier and more expensive than a serverless container platform for a simple web app.

• ✓

  Cloud Run

  Why this is correct

  Cloud Run is a fully managed serverless container platform that executes stateless HTTP/S containers on demand, automatically scaling from zero to handle traffic spikes and back down to zero when requests stop. It accepts any container image that listens on HTTP/HTTPS, pulled from Artifact Registry or Container Registry, and you are billed only for the resources used during request processing (increments of 100ms) with no charge for idle instances. This makes it a direct fit for a containerized web application that needs elastic scaling and pay-per-use pricing without the need to manage clusters or nodes.

• ✗

  Compute Engine with Preemptible VMs

  Why it's wrong here

  Preemptible VMs are low-cost, interruptible instances that Google can terminate at any time when capacity is reclaimed, typically within 24 hours, making them unreliable for a user-facing web application without additional failover logic. They are billed per second while in a RUNNING state, so you pay for every active VM even during periods of zero traffic, and they do not automatically scale to zero. You also have to build and manage your own autoscaling and instance recreation mechanisms, which is neither serverless nor cost-effective for an application that should scale down completely when idle.

Go deeper

Related to this question