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

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

A software team deploys microservices using containers and wants Google Cloud to automatically manage the scaling, self-healing, and rollout of their containerized applications. They don't want to provision or manage underlying virtual machines. Which Google Cloud service best meets this need?

⚠ Common exam trap

It's easy for candidates to confuse Compute Engine (IaaS) with a managed container service, or assume Cloud Storage or Cloud CDN can orchestrate containers, when only GKE provides the automated lifecycle management described.

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

Google Kubernetes Engine (GKE), which manages containerized applications with automatic scaling, self-healing, and rolling updates

Google Kubernetes Engine (GKE) is the correct choice because it provides a managed Kubernetes environment that automates scaling, self-healing (e.g., automatic pod restarts and node repair), and rollout management (e.g., rolling updates and rollbacks) for containerized applications. This meets the requirement of not provisioning or managing underlying virtual machines, as GKE abstracts the node infrastructure.

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, Google Cloud's virtual machine service

    Why it's wrong here

    Compute Engine offers Infrastructure-as-a-Service virtual machines that give teams full control over the OS and runtime, but it does not natively manage containerized applications. To run containers, you must install Docker and a clustering tool like Kubernetes yourself, then manually configure node pools, health checks, autoscaling, and rolling update strategies. This operational burden clashes with the need for automatic scaling, self-healing, and managed rolling updates, making it an unsuitable choice for a fully managed container platform.

  • Google Kubernetes Engine (GKE), which manages containerized applications with automatic scaling, self-healing, and rolling updates

    Why this is correct

    Google Kubernetes Engine (GKE) is a managed Kubernetes service that automates container orchestration, including deployment, scaling, and operations. It provides managed node pools with cluster autoscaling, health checks that automatically reschedule unhealthy pods, and rolling updates with configurable surge and unavailable budgets. Teams only define the desired application state via Deployments and HorizontalPodAutoscaler resources, and GKE continually reconciles the actual cluster state to match, fulfilling all requirements for automatic scaling, self-healing, and rolling updates.

  • Cloud Storage, for storing container images and serving them to instances

    Why it's wrong here

    Cloud Storage is a durable object storage service for unstructured data, not a container registry or a runtime environment. Container images are layered filesystems that must be stored in a service like Artifact Registry, which integrates with GKE for authentication, vulnerability scanning, and efficient pulling. Cloud Storage cannot execute containers, schedule pods, or manage application lifecycles, and while it could technically host a tarball of an image, it lacks the registry API and orchestration capabilities needed for this use case.

  • Cloud CDN, which distributes containerized applications globally

    Why it's wrong here

    Cloud CDN is a global content delivery network that caches static resources such as images, CSS, and JavaScript at edge locations to reduce latency. It cannot distribute or execute containerized applications because it lacks a control plane for scheduling, service discovery, or pod lifecycle management. While it can accelerate delivery of front-end assets, it does not orchestrate containers or provide self-healing or rolling updates.

Go deeper

Related to this question

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.