Which type of Service does not have a ClusterIP?

Correct answer: ExternalName

Option C is correct because an ExternalName Service maps a Kubernetes Service name to an external DNS name using a CNAME record, and it does not allocate a ClusterIP address since it proxies traffic at the DNS level rather than through kube-proxy. Option A, NodePort, builds on top of ClusterIP and always has a ClusterIP assigned in addition to its node-level port. Option B, ClusterIP, is the default Service type and is defined by having a ClusterIP; by definition it cannot lack one. Option D, LoadBalancer, also builds on ClusterIP and NodePort, so it inherits a ClusterIP and additionally provisions an external load balancer.