Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions
A company runs many containerized microservices that need orchestration — automatic scheduling, scaling, self-healing, and rolling updates. They want a managed service so they don't maintain the control plane themselves. Which Google Cloud service is purpose-built for this?
⚠ Common exam trap
The GCDL exam often tests the distinction between serverless container platforms (Cloud Run) and full container orchestration (GKE), where candidates mistakenly choose Cloud Run because it also runs containers, but it lacks the orchestration features like manual scaling, self-healing, and rolling updates that GKE provides.
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)
Google Kubernetes Engine (GKE) is a managed Kubernetes service that provides automatic orchestration, scaling, self-healing, and rolling updates for containerized microservices. It fully manages the Kubernetes control plane, including the API server, etcd, and scheduler, so the customer does not have to maintain them. This makes GKE the purpose-built solution for the described requirements.
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 Run
Why it's wrong here
Cloud Run is a serverless compute platform that executes stateless containers in a fully managed environment, scaling automatically based on HTTP traffic and abstracting away infrastructure concerns like cluster management. However, its model is request-driven and per-revision, lacking the native Kubernetes primitives—pod-level scheduling, service discovery via Services, ConfigMaps, persistent volumes, and custom ingress policies—required for orchestrating many interdependent microservices with complex networking and storage needs. GKE provides that cluster-aware control and declarative API, making Cloud Run an inappropriate choice for this scenario.
- ✓
Google Kubernetes Engine (GKE)
Why this is correct
Google Kubernetes Engine (GKE) is a managed Kubernetes service that fully handles the control plane—including the API server, scheduler, and etcd—and optionally the node infrastructure via Autopilot mode, which abstracts node pools and cluster management while exposing the full Kubernetes API. GKE delivers the complete Kubernetes object model (Deployments, Services, StatefulSets, Ingress, ConfigMaps, persistent volumes) enabling declarative deployment, service discovery, auto-scaling, and rolling updates for interdependent microservices. It also integrates deeply with Google Cloud's ecosystem, such as Cloud Load Balancing, Cloud Monitoring, Workload Identity, and multi-cluster gateways, providing the custom networking, storage, and scheduling control that the scenario demands.
- ✗
Cloud Composer
Why it's wrong here
Cloud Composer is a fully managed service built on Apache Airflow for workflow orchestration, meaning it automates pipelines as directed acyclic graphs (DAGs) where the focus is on scheduling and monitoring data jobs, not on managing containerized workloads. It does not schedule pods, maintain container registries, provide service discovery, or offer Kubernetes-native load balancing; its scope is temporal and task-centric. Although Cloud Composer could trigger jobs running on a GKE cluster, it cannot replace the container orchestration layer needed to deploy and manage many interdependent microservices across a cluster.
- ✗
Compute Engine with managed instance groups
Why it's wrong here
A managed instance group (MIG) provides autoscaling, autohealing, and rolling updates for a fleet of identical virtual machines, operating at the IaaS layer. MIGs are not container-aware: they scale and heal entire VMs based on metrics like CPU utilization, offer no pod scheduling or per-container lifecycle management, and lack built-in Kubernetes networking, service discovery, or declarative resource manifests. While it is possible to install containers on these VMs manually, the MIG cannot orchestrate container placement, account for multi-container pods, or apply readiness/liveness probes at the container level—capabilities that GKE provides natively.
Go deeper
Related to this question
Learn chapter
Cloud Digital Transformation
Key term
Service
A service is a software component or system that performs a specific function and is available to be used by other programs or users over a network.
Key term
AKS
Azure Kubernetes Service (AKS) is a managed container orchestration service on Microsoft Azure that simplifies deploying, managing, and scaling containerized applications using Kubernetes.
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 →
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.