Which Kubernetes Service type is invalid?

The correct answer is C. InternalName. InternalName does not exist as a Kubernetes Service type - it's a fabricated option designed to trick test-takers who might confuse it with ExternalName (option D), which is valid and maps a Service to an external DNS name via a CNAME record. The four legitimate Service types…

Explain Container and Kubernetes Concepts

Question

Options

ALoadBalancer
BNodePort
CInternalName
DExternalName
EClusterIP

How the community answered

(59 responses)

A
5% (3)
B
3% (2)
C
90% (53)
D
2% (1)

Explanation

InternalName does not exist as a Kubernetes Service type - it's a fabricated option designed to trick test-takers who might confuse it with ExternalName (option D), which is valid and maps a Service to an external DNS name via a CNAME record.

The four legitimate Service types are:

ClusterIP (E) - the default; exposes the Service on an internal cluster IP only
NodePort (B) - exposes the Service on a static port on every Node's IP
LoadBalancer (A) - provisions an external cloud load balancer, building on top of NodePort
ExternalName (D) - maps to an external DNS name, no proxying involved

Memory tip: Use the acronym CLNE (ClusterIP → LoadBalancer → NodePort → ExternalName) to recall all four valid types. If you see "InternalName" on an exam, it's always the trap - Kubernetes has ExternalName but nothing called InternalName.

Topics

#Kubernetes Services#Service Types#Container Fundamentals

Community Discussion

No community discussion yet for this question.

Full 1V0-71.21 Practice