Several identical web servers should share incoming requests so no one server takes the whole crowd. Which service spreads those requests?
Select an answer to reveal the explanation.
Short Explanation
The crowd should be split across several doors instead of piling into one. You put a load balancer in front of the web servers. A log collector, a mail filter, and a time server do not hand out the next request.
Full Explanation
A load balancer distributes incoming requests across a pool of servers. Identical web servers that should share a crowd need that service in front of them. A syslog server receives log messages. It does not choose which web server handles the next session. A spam gateway filters mail. Web sessions are not mail. An NTP server synchronizes clocks. Accurate time does not spread web traffic. Exam caveat: the balancer's health checks matter. If it keeps sending people to a server that is down, the crowd still sees failures. Operational check: send several test requests and confirm they land on more than one web server. Watch several requests land on more than one server before you call the pool balanced. Take one server out of the pool and confirm new requests stop landing on it. Put the server back in the pool after the test and confirm it takes traffic again.