CKA Services and Networking Practice Question
Which Service type exposes a Service on each Node's IP at a static port in the range 30000-32767?
⚠ Common exam trap
It's easy for candidates to confuse NodePort with LoadBalancer, thinking LoadBalancer also uses the 30000-32767 port range on nodes, but LoadBalancer typically uses a cloud provider's load balancer and does not guarantee a static node port in that range unless NodePort is also specified.
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
✓
NodePort
A NodePort Service exposes the Service on each Node's IP at a static port in the range 30000-32767. When you create a NodePort Service, Kubernetes allocates a port from that range (or you can specify one) and opens that port on every node in the cluster, forwarding traffic to the Service's ClusterIP and then to the selected Pods.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
NodePort
Why this is correct
NodePort exposes the Service on each Node's IP at a static port, which is allocated from a default range of 30000-32767. Kubernetes automatically routes traffic incoming to this port on any node directly to the underlying backend Pods, regardless of which node those Pods are actually running on. This makes the service accessible from outside the cluster using the combination of any Node's IP and the allocated port.
- ✗
ExternalName
Why it's wrong here
ExternalName is a special service type that maps a Kubernetes service to an external DNS name by returning a CNAME record. It does not allocate any cluster IP addresses, proxy traffic, or open ports on the cluster nodes, making it completely unsuitable for exposing internal workloads on node IPs.
- ✗
ClusterIP
Why it's wrong here
ClusterIP is the default Kubernetes service type that exposes the service on an internal IP address. This IP is only reachable from within the Kubernetes cluster, meaning it does not expose any ports on the host nodes' external network interfaces for outside access.
- ✗
LoadBalancer
Why it's wrong here
LoadBalancer provisions an external load balancer using a cloud provider's API to route traffic into the cluster. While it builds upon NodePort by automatically configuring node ports under the hood, its primary mechanism of exposure is the external IP assigned by the cloud provider rather than the node IPs themselves.
Go deeper
Related to this question
Learn chapter
Kubernetes Architecture Overview
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.
Key term
Network Policies
A Kubernetes resource that controls how pods communicate with each other and with other network endpoints, acting as a firewall for pod-to-pod traffic.
About these practice questions
One of 726 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.