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 Functions

  Why it's wrong here

  Cloud Functions is a serverless execution environment designed for short-lived, event-driven functions triggered by HTTP, Pub/Sub, or storage events. Its default timeouts (maximum 540 seconds) and stateless, single-purpose execution model make it unsuitable for hosting full web applications with long-lived connections, complex routing, or background work. While it exposes an HTTP trigger, it lacks the ability to run an arbitrary containerized web server, so it forces you to restructure the app into function handlers.

• ✓

  Cloud Run

  Why this is correct

  Cloud Run is a managed serverless compute platform that runs stateless containers directly on an HTTPS endpoint, making it ideal for web applications. It supports any framework or language because you package your app as a container, automatically scales to zero when idle, and charges only for compute resources during request processing. This combination of full control over the runtime and per-invocation billing delivers both developer convenience and cost efficiency for quickly deploying web services.

• ✗

  Compute Engine

  Why it's wrong here

  Compute Engine is an IaaS offering that requires you to provision, patch, and manage individual VM instances, including capacity planning, availability zones, and the OS. It is not serverless, so you are billed for the allocated vCPUs and memory even when the instance sits idle, and you must handle horizontal scaling manually via instance groups or load balancers. This operational overhead contradicts the startup's goal of quickly deploying a web application without worrying about infrastructure.

• ✗

  Google Kubernetes Engine (GKE)

  Why it's wrong here

  Google Kubernetes Engine is a managed Kubernetes service, but it still requires you to manage a cluster of node VMs, configure autoscaling, and monitor node health; even with features like Autopilot, you are paying for node capacity rather than per request. Kubernetes introduces complexity with YAML manifests, namespaces, and networking policies that is unnecessary for a simple web application, and the control plane's ongoing operational burden makes it a slower and more error-prone path for a startup aiming for speed. It is overkill compared with a fully managed serverless platform.

Go deeper

Related to this question