Cloud Digital Leader Fundamental Cloud Concepts 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.

• ✗

  Compute Engine

  Why it's wrong here

  Compute Engine is a raw IaaS offering that requires you to provision and manage virtual machines, including OS patching, firewall rules, and instance health. For a containerized web app, you'd have to either install a container runtime yourself or run a container-optimized OS, but you still pay for the VM even when no traffic arrives, and you must manually configure autoscaling. This operational overhead and idle-cost model conflict with the startup's need for a simple, pay-for-use platform.

• ✗

  Google Kubernetes Engine (GKE)

  Why it's wrong here

  Google Kubernetes Engine itself is a managed Kubernetes service, but that does not mean it is serverless: you must create and pay for a node pool of VMs to run your workloads, and you're responsible for cluster sizing, node upgrades, and horizontal pod autoscaling. For a single containerized web application, GKE introduces substantial complexity and a baseline cost for the nodes that runs 24/7, even when the app is idle. Unless the startup needs Kubernetes-native features like custom resourcing, service mesh, or multi-container orchestration, GKE is overkill.

• ✗

  App Engine Standard

  Why it's wrong here

  App Engine Standard is a serverless platform, but its standard environment historically supports only specific language runtimes (e.g., Python, Java, Go) and bundles dependencies in a proprietary sandbox; it does not accept arbitrary Docker containers. To run a truly custom container, you would need App Engine Flexible, which uses GCE VMs and thus does not scale to zero as quickly and has a different billing model (you still pay for the underlying VM when no traffic arrives). Given the startup's containerized application, App Engine Standard is either incompatible or forces a rewrite to fit its supported runtimes.

• ✓

  Cloud Run

  Why this is correct

  Cloud Run is a fully managed, serverless container platform that executes your container only when requests arrive, scaling up automatically to handle traffic and scaling down to zero when idle, so you are billed only for the time during which a request is being processed (measured to 100ms granularity). It leverages Knative on Google Kubernetes Engine under the hood but removes all cluster management from your purview, letting you deploy a container image directly to a URL. For a startup running a containerized web app, this delivers the lowest operational overhead and the most cost-efficient pay-per-request model while supporting any container runtime that listens on HTTP.

Go deeper

Related to this question