Bird
0
0

You created a NodePort service but cannot access your app externally. Which is the most likely cause?

medium📝 Troubleshoot Q14 of 15
Kubernetes - Services
You created a NodePort service but cannot access your app externally. Which is the most likely cause?
AThe pod selector labels do not match any pods
BAll of the above
CThe service type is set to ClusterIP instead of NodePort
DThe <code>nodePort</code> value is outside the allowed range (30000-32767)
Step-by-Step Solution
Solution:

  1. Step 1: Check nodePort range validity

    NodePort must be between 30000 and 32767; outside this range causes failure.

  2. Step 2: Verify pod selector and service type

    If selector labels don't match pods or service type is not NodePort, external access fails.

  3. Step 3: Combine all issues

    Any of these issues can cause access failure, so all are likely causes.

  4. Final Answer:

    All of the above -> Option B

  5. Quick Check:

    Invalid port, selector, or type = no external access [OK]
Quick Trick: Check port range, selector labels, and service type [OK]
Common Mistakes:
  • Ignoring nodePort range limits
  • Not verifying pod labels match selector
  • Assuming service type is correct without checking

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
Namespaces - Resource quotas per namespace - Quiz 13medium Namespaces - Resource quotas per namespace - Quiz 2easy Pods - Viewing Pod details and logs - Quiz 4medium Pods - Init containers - Quiz 14medium Pods - Init containers - Quiz 9hard Pods - Why Pods are the smallest deployable unit - Quiz 7medium Services - Service discovery via DNS - Quiz 7medium kubectl Essential Commands - kubectl port-forward for local access - Quiz 14medium kubectl Essential Commands - kubectl exec for container access - Quiz 10hard kubectl Essential Commands - kubectl get for listing resources - Quiz 4medium