Which service is commonly deployed behind a Network Load Balancing (NLB) farm to improve availability?

• A. Email storage servers.
• B. Public web servers.
• C. DHCP servers.
• D. Print servers.

Answer: (B)

Network Load Balancing spreads incoming requests across multiple servers to keep a service available even if one server fails. The most common target for an NLB cluster is public web servers, because web traffic is typically high and stateless enough that any healthy node can handle an incoming request. This makes it easy to route users to another server transparently when one node goes down, boosting both availability and your ability to handle traffic spikes.

Other services aren’t as naturally suited to NLB in the same way. DHCP servers rely on local subnet coordination and broadcast protocols, so they aren’t typically placed behind an NLB. Print servers depend on a queueing model that isn’t easily distributed with basic load balancing. Email storage can involve stateful storage and complex routing, which is better handled with specialized clustering or storage/load-forwarding approaches rather than standard NLB.