Bird
0
0

Why is the LoadBalancer service type often unsuitable for exposing services in an on-premises Kubernetes cluster without cloud provider integration?

hard📝 Conceptual Q10 of 15
Kubernetes - Services
Why is the LoadBalancer service type often unsuitable for exposing services in an on-premises Kubernetes cluster without cloud provider integration?
ABecause it requires cloud provider APIs to provision external load balancers automatically
BBecause it only supports internal cluster IPs without external access
CBecause it cannot expose services on NodePorts
DBecause it automatically disables pod selectors
Step-by-Step Solution
Solution:
  1. Step 1: Understand LoadBalancer dependencies

    LoadBalancer service type depends on cloud provider APIs to create external load balancers.
  2. Step 2: On-premises limitations

    Without cloud integration, Kubernetes cannot provision external IPs, so LoadBalancer services remain pending.
  3. Step 3: Evaluate other options

    NodePort and ClusterIP do not require cloud APIs; pod selectors are unrelated.
  4. Final Answer:

    Because it requires cloud provider APIs to provision external load balancers automatically -> Option A
  5. Quick Check:

    LoadBalancer needs cloud APIs, missing on-premises [OK]
Quick Trick: LoadBalancer needs cloud APIs, missing on-premises clusters [OK]
Common Mistakes:
  • Thinking LoadBalancer works without cloud provider
  • Confusing NodePort with LoadBalancer capabilities
  • Assuming LoadBalancer disables selectors

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes