Bird
0
0

Why does a headless service in Kubernetes not allocate a cluster IP, and how does this affect service discovery?

hard📝 Conceptual Q10 of 15
Kubernetes - Services
Why does a headless service in Kubernetes not allocate a cluster IP, and how does this affect service discovery?
ATo reduce network traffic; service is disabled
BTo allow direct pod access; DNS returns pod IPs instead of a cluster IP
CTo enable external load balancers; service IP is external
DTo improve security; service IP is hidden
Step-by-Step Solution
Solution:

  1. Step 1: Understand cluster IP allocation in headless services

    Headless services do not get a cluster IP to avoid load balancing and allow direct pod communication.

  2. Step 2: Effect on DNS and service discovery

    DNS returns individual pod IPs, enabling clients to discover and connect directly to pods.

  3. Final Answer:

    No cluster IP allows direct pod access; DNS returns pod IPs -> Option B

  4. Quick Check:

    Headless no cluster IP = direct pod DNS [OK]
Quick Trick: No cluster IP means DNS returns pod IPs for direct access [OK]
Common Mistakes:
  • Thinking headless disables service
  • Assuming external load balancer is involved
  • Believing cluster IP is hidden for security

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Why container orchestration matters - Quiz 15hard Labels and Selectors - Label selectors (equality, set-based) - Quiz 15hard Namespaces - Switching namespace context - Quiz 2easy Namespaces - Resource quotas per namespace - Quiz 10hard Namespaces - Resource quotas per namespace - Quiz 12easy Namespaces - Switching namespace context - Quiz 15hard Namespaces - Default namespaces overview - Quiz 15hard Pods - Init containers - Quiz 7medium Services - Service selectors and labels - Quiz 2easy kubectl Essential Commands - kubectl apply vs create - Quiz 14medium