GCP - Cloud Load Balancing
A developer configures an Internal TCP/UDP Load Balancer but backend instances do not receive traffic. What is the most probable cause?
A developer configures an Internal TCP/UDP Load Balancer but backend instances do not receive traffic. What is the most probable cause?
medium📝 Conceptual Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand Internal TCP/UDP LB scope
It works only within a single VPC network.Step 2: Check backend instance placement
If instances are outside the VPC, traffic won't reach them.Final Answer:
Backend instances are not in the same VPC network -> Option AQuick Check:
Internal LB requires backend instances in same VPC [OK]
Quick Trick: Internal LB requires backend in same VPC [OK]
Common Mistakes:
- Using global forwarding rule for internal LB
- Ignoring health checks impact
- Confusing protocol types for load balancer
Master "Cloud Load Balancing" in GCP
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore GCP Quizzes