You have just set up a classic load balancer with EC2 Instances distributed over 2 subnets.
The first subnet has one instance and the other subnet has 3 instances.
You have noticed that the load is high on the single instance located in the first subnet.
Which of the following settings can be set on the load balancer to ensure even distribution of traffic across all of the instances.
Click on the arrows to vote for the correct answer
A. B. C. D.Answer - D.
The AWS documentation mentions the following.
If the load balancer nodes for your Classic Load Balancer can distribute requests regardless of Availability Zone, this is known as cross-zone load balancing.
With cross-zone load balancing enabled, your load balancer nodes distribute incoming requests evenly across the Availability Zones enabled for your load balancer.
For more information on cross zone load balancing, please visit the below link:
http://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-disable-crosszone-lb.htmlThe correct answer to this question is D. Configure Cross-Zone Load Balancing.
When you set up a classic load balancer, it distributes incoming traffic across all of the registered instances in the same Availability Zone as the load balancer. By default, a classic load balancer does not distribute traffic across multiple Availability Zones. This is where the Cross-Zone Load Balancing feature comes in.
Cross-Zone Load Balancing ensures that the incoming traffic is evenly distributed across all of the registered instances in all of the Availability Zones that are enabled for your load balancer. When this feature is enabled, the load balancer distributes the traffic across all of the registered instances in all of the enabled Availability Zones, instead of just within a single Availability Zone. This helps to prevent one Availability Zone from becoming overloaded with traffic, which can cause a decrease in performance.
In this scenario, enabling Cross-Zone Load Balancing would help to ensure that the incoming traffic is evenly distributed across all of the registered instances, including the one in the first subnet that is currently receiving a high load. This would help to prevent that instance from becoming overwhelmed and ensure that all of the instances are handling a similar amount of traffic.
Connection draining (option A) is a feature that allows the load balancer to complete in-flight requests on a deregistering instance before removing it from service. Sticky sessions (option B) is a feature that allows the load balancer to bind a user's session to a specific instance, which can be useful for certain types of applications but does not address the issue of uneven traffic distribution. Proxy protocol (option C) is a feature that allows the load balancer to include additional information about the client connection in the request headers, but is not directly related to traffic distribution.