ComputeSphereLearn
Console
Learning paths / Cloud foundations / Load balancers and private networks

Check: load balancers and private networks

Knowledge check · 5 min · Module 8, lesson 4 of 45 min left in this module

Module 8 · Load balancers and private networksLesson 4 of 4

Goal: Confirm you can explain how a load balancer routes traffic and decide what should be public, private or allowlisted.

Five questions: four on this module, one on Module 6. Every answer explains itself, right or wrong.

One of your four servers starts failing its health check. What happens to requests?
Your app writes uploaded photos to its own server's disk. Behind a load balancer, users sometimes can't find their photo. Why?
Your database is at 10.0.2.20 on the private network. Someone at home tries to connect to it directly. What happens?
An admin panel must be reachable from your office only, which has the fixed address 203.0.113.7. What do you add?
From Module 6: your load balancer answers 502 Bad Gateway. What does that tell you?

Retry as often as you like.

Before you go, name each part.

Load balancers and private networks at a glance: from memory

Name each part before you reveal it.

One public entry that spreads requests.
Keeps traffic off failing servers.
Addresses the internet can't reach.
How services find each other inside.
Only listed addresses may connect.
What sits between the internet and your servers.