KCNA Kubernetes Fundamentals Practice Question
You have a Deployment that runs a web application. You need to expose this application externally on a fixed port using a cloud load balancer. Which Service type should you use?
⚠ Common exam trap
CNCF often tests the misconception that NodePort is sufficient for external access, but the question's requirement for a 'cloud load balancer' and 'fixed port' (like 80/443) disqualifies NodePort because it uses a high port range and lacks cloud LB integration.
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
A LoadBalancer Service type provisions an external cloud load balancer (e.g., AWS ELB, GCP TCP/UDP Load Balancer) that exposes the application on a fixed port (typically 80/443) and distributes traffic to the Pods. This is the correct choice because the requirement explicitly asks for a cloud load balancer with a fixed external port, which is exactly what LoadBalancer provides by integrating with the underlying cloud provider's API.
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 opens a static port on every node, but it does not provision a cloud load balancer, and the port range is restricted rather than freely fixed. It is tempting because it does expose the application externally. It suits bare-metal or manual load balancing, not the cloud load balancer the stem requires.
- ✓
LoadBalancer
Why this is correct
A LoadBalancer Service provisions an external cloud load balancer and assigns a stable, externally reachable IP, satisfying the requirement to expose the application externally on a fixed port. Unlike NodePort, which opens a port on every node, it integrates directly with the cloud provider's load-balancing infrastructure.
- ✗
ExternalName
Why it's wrong here
ExternalName maps a Service to a DNS CNAME record and creates no proxy or load balancer, so it cannot publish a fixed port externally. It is tempting as the only type with 'External' in its name. It is correct when aliasing an in-cluster Service to an external DNS name, not for exposing pods.
- ✗
ClusterIP
Why it's wrong here
ClusterIP assigns a virtual IP reachable only inside the cluster, so external clients cannot connect at all. It is tempting because it is the default Service type and backs every other type. It is the right choice for internal pod-to-pod communication, not for cloud load balancer exposure.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-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 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.