CKA Services and Networking Practice Question
What is the purpose of a Headless Service (clusterIP: None)?
⚠ Common exam trap
Candidates often confuse a Headless Service with a regular ClusterIP Service, thinking it still provides load balancing or a stable virtual IP, when in fact it disables both and returns all pod IPs for direct pod-to-pod communication.
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
✓
To allow DNS queries to return all pod IPs for a StatefulSet
A Headless Service (clusterIP: None) is used when you want to discover individual pod IPs directly, rather than having a single virtual IP load-balance traffic. When a Service has clusterIP set to None, DNS queries return the A/AAAA records for all ready pod IPs, which is essential for StatefulSets where each pod has a unique identity and needs to be addressed individually, such as in clustered databases like Cassandra or Kafka.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
To allow DNS queries to return all pod IPs for a StatefulSet
Why this is correct
A headless Service (spec.clusterIP: None) allocates no ClusterIP, so kube-proxy provides no virtual IP or load balancing. Instead, the DNS entry for the Service resolves to the set of individual Pod IPs backing that Service; for a StatefulSet, this enables clients and peers to discover and connect directly to every Pod, including via stable names like pod-0.svc.namespace.svc.cluster.local. This is the standard cluster-internal pattern for stateful discovery (e.g., databases), not a stable front-end VIP.
- ✗
To expose the Service externally via a cloud load balancer
Why it's wrong here
A Service of type LoadBalancer provisions a cloud load balancer (e.g., an AWS ELB or GCP LB) and assigns an external, reachable IP address. A headless Service has no ClusterIP and is not proxied by kube-proxy, so it cannot be exposed externally via a load balancer route. External exposure is the responsibility of LoadBalancer or NodePort types, so choosing clusterIP: None is unrelated to that purpose.
- ✗
To provide load balancing across pods
Why it's wrong here
With a regular ClusterIP Service, kube-proxy distributes traffic among healthy endpoints, giving you load balancing across pods. A headless Service deliberately removes that virtual IP, so DNS returns multiple A records and the client chooses which Pod to contact—the platform performs no load spreading. Headless Services therefore do not provide load balancing; they expose all backing pod IPs to the querier.
- ✗
To assign a static ClusterIP
Why it's wrong here
clusterIP: None is the exact opposite of a static ClusterIP. A static ClusterIP is set by explicitly assigning a specific address in spec.clusterIP on a normal ClusterIP Service, giving it a fixed internal VIP. A headless Service requests that no ClusterIP be allocated at all, so its DNS records point directly to endpoints instead of to a single virtual address.
Visual reference
Go deeper
Related to this question
Learn chapter
Deployments and ReplicaSets
Key term
StatefulSets
A Kubernetes resource that manages stateful applications by providing stable network identities and persistent storage for each pod.
Key term
ClusterIP NodePort LoadBalancer
ClusterIP, NodePort, and LoadBalancer are three types of Kubernetes Services that control how traffic reaches your application pods inside the cluster or from outside.
About these practice questions
One of 302 original CKA 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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CKA practice question is part of Courseiva's free CNCF 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 CKA exam.