Bird
0
0

You created an ExternalName service but pods cannot resolve the service name. What is the most likely cause?

medium📝 Troubleshoot Q6 of 15
Kubernetes - Services
You created an ExternalName service but pods cannot resolve the service name. What is the most likely cause?
AThe externalName field is missing or incorrect
BThe service selector is not matching any pods
CThe service type is set to ClusterIP instead of ExternalName
DThe service port is not defined
Step-by-Step Solution
Solution:

  1. Step 1: Identify cause of DNS resolution failure

    If pods cannot resolve the ExternalName service, the externalName field is likely missing or has a wrong DNS name.

  2. Step 2: Understand irrelevant fields

    Selector and ports do not affect ExternalName DNS resolution. Service type must be ExternalName, but missing externalName is the main cause.

  3. Final Answer:

    The externalName field is missing or incorrect -> Option A

  4. Quick Check:

    Missing externalName causes resolution failure [OK]
Quick Trick: Check externalName spelling if DNS fails [OK]
Common Mistakes:
  • Checking selectors which are ignored
  • Changing service type unnecessarily
  • Expecting ports to affect DNS

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