Match each Google Kubernetes Engine (GKE) concept to its definition.
Drag a concept onto its matching description — or click a concept then click the description.
Smallest deployable unit, one or more containers
Exposes a set of pods as a network service
Declarative update for pods and ReplicaSets
A worker machine in a Kubernetes cluster
Set of nodes managed by the control plane
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Pod: Smallest deployable unit that runs one or more containers.
In GKE, a Pod is the smallest unit, a Service provides stable network access to Pods, a Deployment manages Pod updates, and a Node is a worker machine. Common confusions involve swapping Pod and Service definitions.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Pod: Smallest deployable unit that runs one or more containers.
Why this is correct
In Kubernetes, a Pod is the smallest and most basic deployable object, representing a single instance of a running process. Unlike a container, which is just a runtime execution unit, a Pod encapsulates one or more containers that share the same network namespace, storage volumes, and lifecycle, so they are always co-located and co-scheduled. The containers inside a Pod can communicate via localhost, and the Pod is the atomic unit of scheduling and scaling in a GKE cluster.
Service: An abstraction that defines a logical set of Pods and a policy to access them.
Why this is correct
A Service is a Kubernetes resource that provides a stable virtual IP (ClusterIP) or DNS name for a dynamic set of Pods matched by label selectors. Because Pods are ephemeral and can be recreated with different IP addresses, a Service decouples clients from the underlying Pod endpoints, enabling load balancing and failover. Service types like ClusterIP, NodePort, LoadBalancer, and ExternalName allow you to expose applications both internally within the cluster and externally to the internet.
Deployment: Provides declarative updates for Pods and ReplicaSets.
Why this is correct
A Deployment is a higher-level controller that manages ReplicaSets and provides declarative updates and rollback capabilities for stateless workloads. When you change the Pod template in the Deployment spec, it triggers a rolling update that creates a new ReplicaSet and gradually scales it up while scaling down the old ReplicaSet, ensuring availability. Deployments also support automatic rollback to a previous revision, self-healing rescheduling of failed Pods, and horizontal scaling of replicas in response to load.
Node: A worker machine in a Kubernetes cluster.
Why this is correct
A Node is a worker machine, either physical or virtual, in a Kubernetes cluster that hosts Pods by running the container runtime and the kubelet agent. Each Node is registered with the cluster and must also run kube-proxy to manage network rules. In GKE, Nodes are Compute Engine VM instances managed by managed instance groups, and the control plane automatically handles Node health, upgrades, and repair through the managed node pool functionality.
Pod: An abstraction that defines a logical set of Pods and a policy to access them.
Why it's wrong here
This definition incorrectly assigns the role of a Service to a Pod. A Pod is not an abstraction defining access policies or a logical set of other Pods; it is the smallest compute unit that directly runs containers. The statement confuses the stable networking abstraction (Service) with the underlying workload execution unit (Pod). In practice, a Pod provides no stable endpoint and is not intended to define access rules—those are handled by Services using label selectors.
Service: Smallest deployable unit that runs one or more containers.
Why it's wrong here
This statement confuses a Pod with a Service. A Service is not a deployable unit that runs containers; it is a pure API abstraction that maps a stable IP address or DNS name to a set of Pod endpoints. Services exist to route traffic to selected Pods and do not execute any processes. The smallest deployable unit in Kubernetes is always a Pod, and the containers within that Pod are the actual running processes.
Go deeper
Learn chapter
Google Cloud Platform Overview
Key term
Google Kubernetes Engine
Google Kubernetes Engine (GKE) is a managed Kubernetes service on Google Cloud that lets you deploy, scale, and manage containerized applications without having to operate the underlying cluster control plane.
Key term
GKE
GKE is Google's managed Kubernetes service that automates deploying, scaling, and managing containerized applications in the cloud.
About these practice questions
One of 769 original ACE practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ACE 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 ACE exam.