Match each Google Cloud serverless compute option to its characteristic.
Drag a concept onto its matching description — or click a concept then click the description.
Event-driven, short-lived functions
Container-based, scales to zero
Platform as a Service (PaaS) with automatic scaling
Orchestration of services and APIs
Event routing and management service
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Cloud Functions: Executes code in response to events, scaling to zero when idle.
The correct matches are: Cloud Functions for event-driven execution, Cloud Run for containerized HTTP services, and App Engine for managed web applications. Common confusions involve swapping the event-driven nature of Cloud Functions with the container-based approach of Cloud Run, or pairing App Engine with event-driven triggers instead of web app hosting.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Cloud Functions: Executes code in response to events, scaling to zero when idle.
Why this is correct
Cloud Functions is Google Cloud's event-driven serverless compute service: you deploy a single purpose-built function (in Node.js, Python, Go, etc.) that executes only when a specified trigger fires, such as a Pub/Sub message, Cloud Storage object change, or HTTP call. The platform auto-provisions and scales the execution environment, and when no events are coming in, the function instances are completely torn down, scaling to zero so you incur no cost or resource usage. This makes it ideal for glue logic, lightweight integrations, and asynchronous background jobs.
Cloud Run: Runs stateless containers that can scale to zero, invoked via HTTP requests.
Why this is correct
Cloud Run runs stateless, pre-built container images on a fully managed, autoscaling infrastructure where each container instance is invoked via standard HTTP/HTTPS requests. It automatically scales up and down based on incoming traffic, and can scale to zero when there are no requests, meaning the service costs nothing until a request arrives. Because it executes a container, you can bring any language, framework, or binary that can listen on a port, making it a flexible bridge between containers and serverless for web APIs and microservices.
App Engine: Fully managed platform for building web applications with automatic scaling.
Why this is correct
App Engine is a fully managed platform-as-a-service (PaaS) that abstracts away the underlying VM and infrastructure so you can focus on writing application code. It provides automatic scaling and load balancing based on HTTP traffic, supports multiple popular programming languages and runtimes (e.g., Java, Python, Go, PHP, Node.js), and includes features like versioning, traffic splitting, and integrated services like Datastore and Memcache. It is designed specifically for building and scaling web applications end-to-end, without requiring you to manage containers or clusters.
Cloud Functions: Runs containerized applications in a managed environment.
Why it's wrong here
This option misattributes a container-centric capability to Cloud Functions. Cloud Functions is function-based: you upload discrete functions that are executed in a managed runtime for short-lived, event-driven tasks, and you never package your own container. The description of running containerized applications in a managed environment points instead to Cloud Run, which accepts a container image and handles its execution and scaling. Mixing these definitions is a classic source of confusion in serverless compute.
Cloud Run: Fully managed platform that supports multiple programming languages for web apps.
Why it's wrong here
This description actually applies to App Engine, not Cloud Run. While Cloud Run does support multiple programming languages indirectly—because any language can be packaged into a container—it is fundamentally a container execution platform that requires you to build and deploy a container image. In contrast, App Engine directly supports multiple runtime interpreters and manages the web application stack for you, so you simply write code in your chosen language and deploy it. Cloud Run's core distinguishing characteristic is its container-based, HTTP-triggered model, not multi-language platform support.
App Engine: Event-driven, short-lived execution of code in response to triggers.
Why it's wrong here
This option swaps Cloud Functions' event-driven, short-lived execution model onto App Engine. App Engine is a persistent web application platform: it runs long-lived services that handle continuous HTTP traffic, with automatic scaling but not execution that ends after a trigger. The description of executing code in response to events, scaling to zero when idle, and being short-lived exactly matches Cloud Functions, not App Engine. App Engine services are designed to stay up and serve user requests, not to fire on one-time events.
Quick reference
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Learn chapter
Cloud Digital Transformation
Key term
App Engine
App Engine is a fully managed serverless platform from Google Cloud that lets developers build and deploy applications without worrying about the underlying infrastructure.
Key term
Cloud Functions
Cloud Functions are serverless compute services that let you run single-purpose code in response to events without managing servers.
About these practice questions
This GCDL question is part of Courseiva's 829-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.