Bird
0
0

You created a Service but it is not routing traffic to pods. Which of these is the most likely cause?

medium📝 Troubleshoot Q14 of 15
Kubernetes - Services
You created a Service but it is not routing traffic to pods. Which of these is the most likely cause?
AThe Service IP address is manually set incorrectly.
BThe Service selector labels do not match any pod labels.
CPods have static IPs that conflict with the Service IP.
DThe Service type is set to ExternalName.
Step-by-Step Solution
Solution:

  1. Step 1: Check Service selector and pod labels

    If the selector labels do not match any pod labels, the Service has no endpoints to route traffic to.

  2. Step 2: Understand Service IP and type roles

    Service IP is assigned automatically; manual IP setting is uncommon. ExternalName type routes outside cluster, not to pods.

  3. Final Answer:

    The Service selector labels do not match any pod labels. -> Option B

  4. Quick Check:

    Selector mismatch = no routing [OK]
Quick Trick: Match selector labels exactly to pod labels [OK]
Common Mistakes:
  • Manually setting Service IP address
  • Ignoring selector label mismatch
  • Confusing Service types and their routing

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 15hard Namespaces - Switching namespace context - Quiz 8hard Namespaces - Resource quotas per namespace - Quiz 2easy Pods - Sidecar container pattern - Quiz 12easy Pods - Creating Pods with kubectl - Quiz 5medium ReplicaSets and Deployments - Desired replicas vs actual replicas - Quiz 3easy ReplicaSets and Deployments - Rolling update strategy - Quiz 3easy ReplicaSets and Deployments - ReplicaSet definition - Quiz 4medium kubectl Essential Commands - kubectl apply vs create - Quiz 12easy kubectl Essential Commands - Why kubectl mastery matters - Quiz 11easy