What best describes a Headless service's behavior?

What best describes a Headless service's behavior?

• A. A ClusterIP service that has no IP
• B. A NodePort that exposes a port externally
• C. An ExternalName pointing to a DNS alias
• D. A LoadBalancer without an external IP

Answer: (A)

Headless service means no cluster IP. You create it by setting clusterIP to None, so Kubernetes does not allocate a virtual IP for the service. Instead, the DNS entry for the service returns multiple records pointing to each backing pod, allowing direct access to individual pods or custom load balancing. This is handy with StatefulSets where each pod has a stable identity. Because there is no cluster IP, the service isn’t reached through a single IP and is not typically exposed via a NodePort or LoadBalancer; ExternalName and other patterns describe different mechanisms for DNS-based or external exposure, not headless behavior. So the description that fits is a service without a cluster IP.

Headless service means no cluster IP. You create it by setting clusterIP to None, so Kubernetes does not allocate a virtual IP for the service. Instead, the DNS entry for the service returns multiple records pointing to each backing pod, allowing direct access to individual pods or custom load balancing. This is handy with StatefulSets where each pod has a stable identity. Because there is no cluster IP, the service isn’t reached through a single IP and is not typically exposed via a NodePort or LoadBalancer; ExternalName and other patterns describe different mechanisms for DNS-based or external exposure, not headless behavior. So the description that fits is a service without a cluster IP.