Questão de Networking #019e3a4f

Load balancing is a technique used to distribute incoming network traffic or requests across multiple backend servers or instances of an application. The primary goal is to ensure no single server becomes overwhelmed, thereby improving responsiveness, reliability, and availability.

How it Works: A load balancer sits between clients and backend servers. It receives incoming requests and, based on a configured algorithm (e.g., round-robin, least connections, IP hash), forwards each request to one of the healthy backend instances. This distribution prevents any single instance from being a bottleneck and provides fault tolerance: if an instance fails, the load balancer stops sending traffic to it and redirects requests to the remaining healthy instances.

Why the correct answer is right: The correct statement is "Automatically distribute requests across instances of an application." This precisely captures the essence of load balancing: distributing client requests across multiple application instances to optimize resource use, maximize throughput, and minimize response time.

Why the incorrect answers are wrong:

• "Automatically measure request performance across instances of an application" describes performance monitoring or profiling, not load balancing. While load balancers may collect metrics, their primary function is distribution, not measurement.
• "Automatically distribute requests across different versions of an application" describes canary deployments or A/B testing, not load balancing. Load balancing typically distributes traffic to identical instances of the same version.
• "Automatically distribute instances of an application across the cluster" describes cluster management or orchestration (e.g., Kubernetes scheduling), not load balancing. Load balancing deals with traffic distribution, not instance placement.