Bird
0
0

Given a pod in namespace test running nslookup myservice.test.svc.cluster.local, what output indicates successful DNS resolution?

medium📝 Command Output Q4 of 15
Kubernetes - Services
Given a pod in namespace test running nslookup myservice.test.svc.cluster.local, what output indicates successful DNS resolution?
ATimeout expired
BError: service not found
CName: myservice.test.svc.cluster.local\nAddress: 10.96.0.15
DNo such host
Step-by-Step Solution
Solution:

  1. Step 1: Understand nslookup success output

    Successful DNS resolution shows the service name and its IP address.

  2. Step 2: Identify failure messages

    Errors like 'No such host', 'Timeout expired', or 'service not found' mean DNS failed.

  3. Final Answer:

    Name: myservice.test.svc.cluster.local\nAddress: 10.96.0.15 -> Option C

  4. Quick Check:

    Successful nslookup shows name and IP [OK]
Quick Trick: Success shows name and IP, errors show failure messages [OK]
Common Mistakes:
  • Confusing error messages as success
  • Expecting pod IP instead of service IP
  • Ignoring namespace in DNS name

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Namespaces - Resource quotas per namespace - Quiz 15hard Namespaces - Creating custom namespaces - Quiz 13medium Namespaces - Default namespaces overview - Quiz 8hard Pods - Sidecar container pattern - Quiz 11easy Pods - Pod lifecycle states - Quiz 12easy Pods - Viewing Pod details and logs - Quiz 4medium ReplicaSets and Deployments - Desired replicas vs actual replicas - Quiz 12easy kubectl Essential Commands - kubectl apply vs create - Quiz 2easy kubectl Essential Commands - kubectl exec for container access - Quiz 13medium kubectl Essential Commands - kubectl exec for container access - Quiz 5medium