Load Balancer vs Router/Switch Traffic Distribution

The core concept tested here is traffic distribution versus packet forwarding. The question specifies a scenario where traffic from one source must be sent to multiple servers that run the same service. This is the textbook definition of load balancing, which distributes incoming requests across a pool of backend resources to optimize responsiveness and reliability.

A Load balancer (D) sits between clients and servers, acting as a reverse proxy. It receives the single stream of client requests and redistributes them among the available servers in the pool. Common algorithms include round-robin, least connections, or weighted distribution. This matches the scenario perfectly.

A Router (A) operates at Layer 3 (Network) and forwards packets based on IP addresses to different subnets or networks. While it can route traffic to multiple destinations, its primary function is inter-network connectivity, not distributing load among identical services within a data center.

A Switch (B) operates at Layer 2 (Data Link) and forwards frames based on MAC addresses to specific ports. While modern switches handle high throughput, they do not intelligently distribute traffic across multiple servers running the same application layer service; they simply send frames to the correct physical port. The comment suggesting 'B' confuses general network connectivity with application-level traffic management.

A Firewall (C) controls access based on security policies (allow/deny rules). While some next-generation firewalls have basic load-balancing features, their primary role is security enforcement, not traffic redistribution for performance.

The boundary to remember: Routers and Switches move data from point A to point B. Load Balancers decide which of many possible B's should receive the data from A.