A school wants student web traffic inspected and cached before it goes out to the internet. Which service does that job?
Select an answer to reveal the explanation.
Short Explanation
The students' web traffic should pass a checkpoint that can look at it and keep a copy of what it already fetched. You put a proxy in that path. A balancer, a log server, and a mail filter each do a real job, and none of those jobs is caching and inspecting the web pages.
Full Explanation
A proxy sits in the path of client web requests. It can enforce what may be fetched and it can cache replies so the next student does not pull the same page from the internet again. That is the service the school described. A load balancer spreads traffic across several servers. It does not by itself inspect and cache student browsing. A syslog server receives log messages. Storing a log line is not inspecting the web page the student asked for. A spam gateway filters mail. It is not the cache and policy point for web traffic. Exam caveat: the clients have to be pointed at the proxy, or the proxy has to be inline, or the traffic will walk around it. Operational check: browse from a student PC, confirm the request appears in the proxy log, and confirm a second request for the same page can be served from the cache. Ask a second student for the same page and confirm the proxy can serve it from cache. Block one test site in the proxy and confirm a student PC cannot open it. Check the proxy log for the student account after the test browse.