GCP - Cloud Load Balancing
You configured a TCP Load Balancer but backend instances are not receiving traffic. What is a common misconfiguration to check?
You configured a TCP Load Balancer but backend instances are not receiving traffic. What is a common misconfiguration to check?
medium📝 Debug Q14 of 15
Step-by-Step Solution
Solution:
Step 1: Check health checks configuration
Load balancer only sends traffic to healthy backends. Missing or failing health checks cause no traffic routing.Step 2: Verify backend health status
Ensure health checks are properly configured and passing for backend instances.Final Answer:
Backend instances lack proper health checks -> Option AQuick Check:
Health checks enable traffic routing [OK]
Quick Trick: Always verify backend health checks first [OK]
Common Mistakes:
- Assuming protocol mismatch blocks traffic
- Ignoring health check failures
- Thinking IP must be public for internal 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