Bird
0
0

Why does Kubernetes not allow selectors in ExternalName services?

hard📝 Conceptual Q10 of 15
Kubernetes - Services
Why does Kubernetes not allow selectors in ExternalName services?
ABecause ExternalName services require manual pod management
BBecause selectors are deprecated in all service types
CBecause selectors cause conflicts with cluster IP allocation
DBecause ExternalName services do not select pods but map to external DNS names
Step-by-Step Solution
Solution:

  1. Step 1: Understand role of selectors in services

    Selectors are used to route traffic to pods inside the cluster.

  2. Step 2: Understand ExternalName service behavior

    ExternalName services do not route to pods but map service names to external DNS names, so selectors are irrelevant and disallowed.

  3. Final Answer:

    Because ExternalName services do not select pods but map to external DNS names -> Option D

  4. Quick Check:

    Selectors disallowed because ExternalName maps DNS, not pods [OK]
Quick Trick: Selectors route pods; ExternalName maps DNS only [OK]
Common Mistakes:
  • Thinking selectors are deprecated
  • Assuming selectors affect cluster IP
  • Believing ExternalName manages pods

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - Setting up a local cluster (minikube, kind) - Quiz 12easy Kubernetes Fundamentals - Why container orchestration matters - Quiz 7medium Labels and Selectors - Adding labels to resources - Quiz 15hard Namespaces - Switching namespace context - Quiz 8hard Namespaces - Switching namespace context - Quiz 3easy Namespaces - Limit ranges for defaults - Quiz 8hard Pods - Sidecar container pattern - Quiz 2easy Pods - Why Pods are the smallest deployable unit - Quiz 8hard kubectl Essential Commands - kubectl get for listing resources - Quiz 9hard kubectl Essential Commands - kubectl logs for debugging - Quiz 11easy