A startup wants to deploy a containerized web application without managing the underlying infrastructure. They want to only focus on code. Which Google Cloud service is most suitable?
Cloud Run is a fully managed serverless platform that executes stateless containers directly from an image. It abstracts all infrastructure, including servers, OS, and cluster management, and automatically scales from zero to N instances based on incoming traffic. You only pay for resources used while a request is being processed, and it brings your existing Dockerfile-based workflow without requiring Kubernetes or VM administration.
Why this answer
Cloud Run is the correct choice because it is a fully managed serverless platform that executes stateless containers in a request-driven environment, abstracting all infrastructure management. This allows the startup to focus solely on code by deploying container images directly from Artifact Registry or Container Registry, with automatic scaling down to zero when not in use.
Exam trap
The trap here is that candidates often confuse App Engine's automatic scaling with container support, overlooking that App Engine Standard requires specific language runtimes and does not accept arbitrary containers, while Cloud Run provides true container portability without infrastructure management.
How to eliminate wrong answers
Option A is wrong because Google Kubernetes Engine (GKE) requires managing a Kubernetes cluster, including node pools, networking, and scaling policies, which contradicts the requirement to avoid infrastructure management. Option B is wrong because Compute Engine provides virtual machines that demand manual provisioning, patching, and capacity planning, directly opposing the goal of focusing only on code. Option C is wrong because App Engine, while serverless, is a platform-as-a-service that restricts the runtime environment to specific supported languages and runtimes, whereas the startup explicitly wants to deploy a containerized application without such constraints.