KCNA Kubernetes Fundamentals Practice Question
A Service of type ClusterIP is created. What is the default behavior of this Service?
⚠ Common exam trap
Many candidates confuse the default Service type (ClusterIP) with NodePort or LoadBalancer, assuming a Service must be externally accessible by default, but Kubernetes intentionally isolates ClusterIP Services to internal cluster traffic only.
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
✓
It exposes the Service on a cluster-internal IP
A ClusterIP Service is the default Kubernetes Service type, which assigns a virtual IP address reachable only within the cluster. Traffic sent to this IP is load-balanced across the Pods selected by the Service's label selector, using iptables or IPVS rules. No external access is provided unless an Ingress or other mechanism is explicitly configured.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It exposes the Service externally via a cloud load balancer
Why it's wrong here
ClusterIP allocates a virtual IP reachable only inside the cluster, so no cloud load balancer is provisioned. LoadBalancer is the type that does this. The option tempts because cloud load balancers do expose Services externally, but that behaviour belongs to a different Service type, not the ClusterIP default.
- ✗
It exposes the Service on a static port on each node
Why it's wrong here
ClusterIP does not bind a port on each node; that is NodePort, which allocates a static port in the 30000-32767 range. The option tempts because NodePort builds on ClusterIP, so the two are easily conflated. ClusterIP's default is an internal virtual IP, with no node-level port exposure.
- ✗
It routes traffic to Pods based on external DNS names
Why it's wrong here
ClusterIP selects backend Pods by label selector and routes to their IPs, not by external DNS names. External DNS resolution is handled by Ingress or ExternalName Services. The option tempts because Kubernetes DNS does resolve Service names internally, but that is name resolution, not traffic routing based on external DNS.
- ✓
It exposes the Service on a cluster-internal IP
Why this is correct
ClusterIP is the default Service type, allocating a virtual IP reachable only from within the cluster network. It satisfies the scenario's implicit constraint that no external exposure is requested, unlike NodePort or LoadBalancer, which additionally open host ports or provision cloud ingress.
Go deeper
Related to this question
Learn chapter
Cluster Architecture and Lifecycle Management
Key term
ReplicaSet and Replication
A ReplicaSet ensures a specified number of identical pod instances are running at all times in Kubernetes, using replication to maintain availability and stability.
Key term
Kubernetes API Primitives
Kubernetes API Primitives are the basic building blocks that the Kubernetes API uses to represent and manage the state of a cluster, such as Pods, Services, Deployments, and Namespaces.
About these practice questions
Courseiva writes every KCNA question from scratch — 930 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 KCNA 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 KCNA exam.