Connection Draining Time for Class Load Balancer

Answer - B.

The AWS documentation mentions the following on the specifics of connection draining.

When you enable connection draining, you can specify a maximum time for the load balancer to keep connections alive before reporting the instance as de-registered.

The maximum timeout value can be set between 1 and 3,600 seconds (the default is 300 seconds)

When the maximum time limit is reached, the load balancer forcibly closes connections to the de-registering instance.

For more information on the ELB connection draining, please visit the link:

Connection draining is a process that allows the Elastic Load Balancer (ELB) to complete requests that are in progress before it shuts down instances or removes them from the load balancer. This is a critical function for ensuring that the service remains available and performs well while instances are being taken out of service.

In Amazon Web Services (AWS), there are two types of load balancers: Classic Load Balancer (CLB) and Application Load Balancer (ALB). The maximum allowable time available for connection draining on a Classic Load Balancer is 60 minutes, while for an Application Load Balancer it is 120 minutes.

Therefore, the correct answer to the question is option C (2 hours). It is important to note that this value can be configured based on the requirements of the application and the specific use case.

It is also worth mentioning that connection draining is not enabled by default on load balancers, and it must be configured by the user. When configuring connection draining, the user can specify the maximum time allowed for draining connections, as well as the maximum number of connections that can be drained simultaneously. This allows the user to balance the need for keeping the service available with the need for quickly removing instances from the load balancer.