Courseiva
Services and NetworkingeasyMultiple ChoiceObjective-mapped

CKA Services and Networking Practice Question

Which of the following Service types exposes a Service on a static port on each node's IP address?

⚠ Common exam trap

Test-takers frequently confuse NodePort with LoadBalancer, thinking that LoadBalancer also exposes a static port on each node, but LoadBalancer actually delegates external access to an external load balancer and does not guarantee a static port on every node's IP.

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

NodePort is the Service type that exposes a Service on a static port (in the range 30000-32767) on each node's IP address. When a NodePort Service is created, Kubernetes allocates a port from that range and opens that port on every node in the cluster, forwarding traffic to the Service's ClusterIP and then to the pods. This allows external traffic to reach the Service by hitting any node's IP address and the allocated NodePort.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • LoadBalancer

    Why it's wrong here

    A LoadBalancer Service provisions an external IP address and an external load balancer through the underlying cloud provider (e.g., AWS ELB, GCP Load Balancer). While it exposes the service to external traffic, it does so by creating a dedicated, external IP endpoint, not by binding a static port directly on each individual cluster node's IP address. This type is designed for robust, cloud-native external access, abstracting away the underlying node IPs.

  • ExternalName

    Why it's wrong here

    An ExternalName Service does not expose any service on a node's IP address or even within the cluster's network directly. Instead, it functions as a CNAME record within the cluster's DNS, mapping the service's internal name to an arbitrary external DNS name. This allows services within the cluster to reach external services using a familiar Kubernetes service name, without proxying any network traffic itself.

  • NodePort

    Why this is correct

    A NodePort Service allocates a static port from the default range 30000–32767 on every cluster node, binding that port to the Service’s ClusterIP. This directly satisfies the stem’s requirement for a static port exposed on each node’s IP address, distinguishing it from ClusterIP (internal only) and LoadBalancer (cloud‑provisioned external IP).

  • ClusterIP

    Why it's wrong here

    A ClusterIP Service exposes the service on a stable, internal IP address that is only reachable from within the Kubernetes cluster. It provides a virtual IP that pods can use to communicate with each other, but it does not expose the service on any node's IP address or to traffic originating from outside the cluster. Its primary role is to enable internal service discovery and communication.

Go deeper

Related to this question

About these practice questions

Courseiva writes every CKA question from scratch — 302 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 →

How Courseiva writes practice questions · Editorial policy

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.