Cloud Digital Leader Why Cloud Technology Can Transform Business 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.

• ✓

  Cloud Run

  Why this is correct

  Cloud Run is the correct choice because it is a fully managed serverless platform that executes stateless containers in a scale-to-zero model, abstracting away all infrastructure such as clusters, nodes, and VMs. You simply deploy a container image and Cloud Run automatically provisions, scales, and load-balances the instances based on incoming HTTP requests or events, billing only for the resources used during request processing. This makes it ideal for containerized workloads where you want zero cluster management and event-driven autoscaling, without the operational overhead of Kubernetes or virtual machines.

• ✗

  Google Kubernetes Engine (GKE)

  Why it's wrong here

  Google Kubernetes Engine (GKE) provides a robust orchestration layer for containerized applications, but it is not serverless: you must manage or at least configure the cluster, node pools, and autoscaling policies. While GKE offers fine-grained control over networking, storage, and workload placement, that control comes with operational complexity. With GKE you are responsible for patching nodes, optimizing resource requests/limits, and handling cluster upgrades (unless you use Autopilot, which still manages nodes for you). For a company simply wanting to run containers without managing cluster infrastructure, GKE introduces unnecessary complexity compared to Cloud Run.

• ✗

  Compute Engine

  Why it's wrong here

  Compute Engine gives you raw virtual machines on which you can install a container runtime and manage everything yourself, including the OS, Docker daemon, networking, and lifecycle of the containers. It is the least abstracted option for running containerized workloads, requiring you to handle patching, scaling, health checks, and capacity planning manually or via managed instance groups. While it offers maximum flexibility and access to specific machine types, GPUs, or custom networking, it contradicts the goal of simply running containers with minimal operational overhead. Cloud Run eliminates VM management entirely, so Compute Engine is a valid but much more hands-on infrastructure choice.

• ✗

  App Engine

  Why it's wrong here

  App Engine supports deploying containers via App Engine flexible environment, but it is more opinionated: it forces a specific application model, health-check conventions, and a narrower network and filesystem model compared to Cloud Run. In the standard environment you are restricted to supported runtimes and cannot run arbitrary container images without significant adaptation. App Engine is designed around serving web applications with auto-scaling rather than general-purpose container workloads. While it is also serverless, Cloud Run is a better fit when you want to bring any existing container image and run it without rewriting your app to fit App Engine's constraints.

Go deeper

Related to this question