CKA Services and Networking Practice Question
You want to expose an application running in the cluster on a public IP address. Which Service type should you use?
⚠ Common exam trap
Many candidates confuse NodePort with a public IP solution, forgetting that NodePort only exposes the service on node IPs, which are typically private and require an additional load balancer or ingress for public access.
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
✓
LoadBalancer
The LoadBalancer service type provisions an external load balancer (e.g., from a cloud provider) that assigns a public IP address to the service, directing external traffic to the application pods. This is the correct choice when you need a publicly accessible IP address without manual node-level configuration.
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 it's wrong here
NodePort exposes a service on every node's IP address at a static port, typically in the 30000-32767 range. This does not automatically create an external load balancer; you must still set up routing rules, firewall policies, or a separate ingress controller to make the service reachable from the public internet. It is a valid low-level exposure technique but not the automatic public IP solution specified in this scenario.
- ✓
LoadBalancer
Why this is correct
LoadBalancer is the Service type that provisions an external load balancer—often via your cloud provider's API—and assigns it a stable public IP address. It automatically routes incoming traffic to the Service's endpoints and performs health checks, so it is the direct way to expose an application to the internet without manual configuration. This is exactly what is required when "exposing an application running in the cluster" means giving it a routable external endpoint.
- ✗
ExternalName
Why it's wrong here
ExternalName does not expose the application at all; instead, it returns a CNAME record pointing to a DNS name you specify. When a client resolves the Service's DNS name, it receives that CNAME, and traffic is directed to an external hostname, not to a load balancer or cluster pods. It is useful for internal service discovery of external services, but it cannot provide a public IP or load balancing for the application.
- ✗
ClusterIP
Why it's wrong here
ClusterIP is the default Service type and is only reachable from within the cluster. It creates a stable virtual IP that fronts the application pods, but this IP is not routable outside the cluster network. Since the goal is to expose the application externally, ClusterIP would leave it inaccessible to outside clients, making it unsuitable for this task.
Go deeper
Related to this question
About these practice questions
This CKA question is part of Courseiva's 302-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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 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.