Bird
0
0

Why does Kubernetes require the full DNS name including namespace to access a service in another namespace instead of just the service name?

hard📝 Conceptual Q10 of 15
Kubernetes - Namespaces
Why does Kubernetes require the full DNS name including namespace to access a service in another namespace instead of just the service name?
ABecause pods cannot communicate across namespaces at all
BBecause service names are only unique within their namespace
CBecause Kubernetes does not support DNS resolution
DBecause services are not discoverable outside their namespace
Step-by-Step Solution
Solution:

  1. Step 1: Understand service name uniqueness scope

    Service names are unique only within their own namespace, not cluster-wide.

  2. Step 2: Necessity of full DNS name

    Full DNS name including namespace disambiguates services with same name in different namespaces.

  3. Final Answer:

    Because service names are only unique within their namespace -> Option B

  4. Quick Check:

    Service name uniqueness is namespace-scoped [OK]
Quick Trick: Service names are unique only within their namespace [OK]
Common Mistakes:
  • Thinking pods cannot communicate across namespaces
  • Believing Kubernetes lacks DNS support
  • Assuming services are invisible outside namespace

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Kubernetes Fundamentals - What is Kubernetes - Quiz 12easy Labels and Selectors - Organizing with recommended labels - Quiz 11easy Namespaces - Creating custom namespaces - Quiz 1easy Pods - Pod lifecycle states - Quiz 12easy ReplicaSets and Deployments - Recreate update strategy - Quiz 15hard Services - Service discovery via DNS - Quiz 15hard Services - NodePort service type - Quiz 8hard Services - Service selectors and labels - Quiz 7medium Services - Endpoints and endpoint slices - Quiz 1easy kubectl Essential Commands - kubectl exec for container access - Quiz 10hard