Courseiva
Google Cloud products, services, and solutionseasyMultiple ChoiceObjective-mapped

Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions

A company wants to enable its developers to write and run code in various programming languages (Python, Node.js, Go) without provisioning or managing any servers. The code should execute in response to HTTP requests. Which Google Cloud product is designed for this serverless, function-level execution model?

⚠ Common exam trap

Google Cloud often tests the distinction between serverless compute (Cloud Functions) and managed services that still require server management (Compute Engine) or are not compute services at all (Cloud SQL, Persistent Disk), leading candidates to confuse database or storage services with code execution platforms.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Cloud Functions, which executes code functions in response to events or HTTP requests with no server management required

Cloud Functions is the correct choice because it is Google Cloud's event-driven, serverless compute platform that allows developers to write and deploy single-purpose functions in languages like Python, Node.js, and Go. These functions automatically scale and execute in response to HTTP triggers (e.g., HTTP requests) without any server provisioning or management, directly matching the requirement for a function-level execution model.

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, which executes code functions in response to events or HTTP requests with no server management required

    Why this is correct

    Cloud Functions is a serverless Function-as-a-Service (FaaS) platform that lets you deploy individual code functions that automatically run in response to events, including HTTPS requests. It removes all infrastructure management—no servers to provision, no operating systems to patch, and no runtime to install—because the platform handles execution, scaling, and availability. It scales from zero to thousands of concurrent invocations instantly and bills only for actual compute time during execution. This precisely matches the requirement to 'execute code in response to HTTP requests with no server management required'.

  • Compute Engine, which provides virtual machines for running code in any language

    Why it's wrong here

    Compute Engine provides infrastructure-as-a-service (IaaS) virtual machines that afford complete control to run any code in any language. However, to use it for event-triggered HTTP functions, you must provision VM instances, install and configure language runtimes, apply security patches, manage the OS, and set up autoscaling policies to handle variable request loads. You pay for the allocated resources (CPU, memory, persistent disk) whether the code is actively processing requests or idle, and scaling is not automatic or zero-to-zero. This operational burden and cost model are the opposite of serverless, making it an unnecessarily complex alternative to Cloud Functions.

  • Cloud SQL, which runs SQL queries in response to HTTP requests

    Why it's wrong here

    Cloud SQL is a fully managed relational database service (e.g., MySQL, PostgreSQL, or SQL Server) that stores and queries structured data via SQL. It does not execute arbitrary application code; it only runs database operations within the database engine. It cannot be triggered directly by HTTP requests as a general-purpose function, and it has no serverless event-driven model for custom logic. Therefore, it cannot replace a function-as-a-service platform for executing code in response to web requests.

  • Persistent Disk, which stores code that can be executed on demand

    Why it's wrong here

    Persistent Disk is block-level storage that persists data independently of any VM lifecycle. While you could store source code or compiled binaries on a Persistent Disk, the disk itself has no execution engine or runtime to actually run that code; you need a separate compute resource, such as a VM, to mount the disk, load the code into memory, and execute it. This requires manual infrastructure provisioning, OS management, and scaling, which contradicts the serverless, on-demand execution model described in the question.

Quick reference

Cloud Service Model Comparison

ModelYou ManageProvider ManagesExamples
IaaSOS, runtime, apps, dataHardware, hypervisor, networkingEC2, Azure VMs, GCP Compute Engine
PaaSApps and dataOS, runtime, middleware, hardwareElastic Beanstalk, Azure App Service
SaaSData and settings onlyEverything elseMicrosoft 365, Salesforce, Workday
FaaS / ServerlessFunction code onlyInfra, scaling, runtimeLambda, Azure Functions, Cloud Run
CaaSContainers and appsKubernetes, OS, hardwareEKS, AKS, GKE

About these practice questions

Courseiva writes every GCDL question from scratch — 829 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

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.