A company runs a highly available web application on Amazon EC2 instances behind an Application Load Balancer. The company uses Amazon CloudWatch metrics. As the traffic to the web application increases, some EC2 instances become overloaded with many outstanding requests. The CloudWatch metrics show that the number of requests processed and the time to receive the responses from some EC2 instances are both higher compared to other EC2 instances. The company does not want new requests to be forwarded to the EC2 instances that are already overloaded. Which solution will meet these requirements?
Select an option, then click Submit answer.
Reference / correct answer:
Use the least outstanding requests algorithm based on the RequestCountPerTarget and ActiveConnectionCount CloudWatch metrics.
Most accepted answer: B. Use the least outstanding requests algorithm based on the RequestCountPerTarget and ActiveConnectionCount CloudWatch metrics.
Community votes: B=7, D=4
Selected Answer: B Option B is correct because can use "RequestCountPerTarget" to identify the amount of requests for each EC2 instance. Then use "least outstanding requests algorithm" to route to targets with the lowest number of in progress requests. Option D is wrong because "RequestCount" cannot identify the amount of requests for each EC2 instance. "RequestCount" is for the whole ALB. upvoted 11 times Tatai2015 2 years, 2 months ago https://aws.amazon.com/about-aws/whats-new/2019/11/application-load-balancer-now-supports-least-outstanding-requests-algorithm-for-load-balancing-requests/ upvoted 3 times ...
https://aws.amazon.com/about-aws/whats-new/2019/11/application-load-balancer-now-supports-least-outstanding-requests-algorithm-for-load-balancing-requests/ upvoted 3 times
Option B would be the correct choice upvoted 8 times
Selected Answer: D D is correct. https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-cloudwatch-metrics.html ActiveConnectionCount - The total number of concurrent TCP connections active from clients to the load balancer RequestCountPerTarget - The average request count per target, in a target group Both metrics do not show stage of every target. RequestCount - The number of requests processed over IPv4 and IPv6. This metric is only incremented for requests where the load balancer node was able to choose a target. We can say how many requests go to targets. TargetResponseTime - The time elapsed, in seconds, after the request leaves the load balancer until the target starts to send the response headers. We have metric to get statistics for every target/instance. In fact Item D is correct upvoted 1 times
Selected Answer: B Actually ,I now vote for B and not D upvoted 1 times