GCP - Cloud Load Balancing
Why does the HTTP(S) Load Balancer in GCP terminate SSL/TLS connections at the load balancer instead of passing encrypted traffic to backend services?
Why does the HTTP(S) Load Balancer in GCP terminate SSL/TLS connections at the load balancer instead of passing encrypted traffic to backend services?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand SSL termination benefits
Terminating SSL at the load balancer offloads CPU-intensive encryption from backends and allows the load balancer to inspect HTTP headers for routing.Step 2: Evaluate incorrect options
Backends can handle encrypted traffic but it's less efficient, SSL termination does not prevent data access by backends, and not all load balancers require SSL termination.Final Answer:
To offload encryption work from backend instances and enable Layer 7 routing decisions. -> Option AQuick Check:
SSL termination offloads encryption and enables routing [OK]
Quick Trick: SSL termination helps routing and reduces backend load [OK]
Common Mistakes:
- Thinking backends cannot handle encrypted traffic
- Believing SSL termination hides data from backends
- Assuming SSL termination is mandatory for all load balancers
Master "Cloud Load Balancing" in GCP
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore GCP Quizzes