Google ACE Deploying and Implementing a Cloud Solution 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 Flexible Environment

  Why it's wrong here

  App Engine Flexible Environment deploys containers on managed Compute Engine VMs, but it does not support scaling to zero instances; the service guarantees at least one VM is always running, so you pay for idle capacity even when there is no traffic. The platform also introduces version-specific instance configurations and requires manual tuning of min/max instances. For a containerized workload that needs burst scaling and cost-free idle, this is less aligned than a serverless option.

• ✗

  Google Kubernetes Engine (GKE)

  Why it's wrong here

  Google Kubernetes Engine (Standard mode) requires a persistent Kubernetes cluster whose control plane is billed monthly, and each node pool must maintain at least one underlying VM node, making it impossible to achieve true scale-to-zero and zero-cost idle without manually deleting and recreating the cluster. Operating GKE also demands continuous infrastructure management—node upgrades, cluster scaling, and monitoring—which contradicts the goal of minimal operational overhead. While GKE can autoscale workloads, the cluster itself remains an always-on cost center.

• ✗

  Compute Engine with container-optimized OS

  Why it's wrong here

  Compute Engine instances running container-optimized OS (COS) give you a VM that is optimized for containers, but it is still a virtual machine that you must provision, secure, patch, and monitor. It does not provide a built-in scale-to-zero mechanism; you would need to integrate with managed instance groups and autoscaling policies, and even then the instance group usually keeps at least one VM running to serve health checks. This approach incurs operational overhead and does not offer per-request billing or fully automatic scaling.

• ✓

  Cloud Run

  Why this is correct

  Cloud Run is a fully managed serverless platform that executes containers in a stateless, request-driven model: when there are no incoming requests, it can scale the service down to zero instances, so you are not charged for idle resources. It automatically scales up to handle traffic spikes, and billing is based on request duration and CPU/memory usage during active processing, measured in 100ms increments. This makes it the most operationally efficient choice for a containerized web application that expects variable traffic.

Go deeper

Related to this question