Exam AWS-SysOps topic 1 question 795 discussion

Doubt if option A can be done with LEAST amount of effort. Option D uses a more standard setup Anyway targettracking on ALB's RequestCountPerTarget metric is advised by AWS: "We strongly recommend that you use a target tracking scaling policy to scale on a metric like average CPU utilization or the RequestCountPerTarget metric from the Application Load Balancer. " Refer to https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html

Option D involves using a target tracking scaling policy based on the ALB's RequestCountPerTarget metric. This metric measures the number of requests processed per target (EC2 instance) by the ALB. It is a useful metric for scaling because it directly reflects the application's load and the number of incoming requests.

option D

D is the answer

D. Use a target tracking scaling policy based on the ALB's RequestCountPerTarget metric : Seems correct

I'll go with D

The RequestCountPerTarget metric value indicates the average number of requests received by each target in a target group associated with an Application Load Balancer during a specified time period. This metric is an indicator of load on an individual application backend during a given time window and can be used by Auto Scaling or your own custom scaling system to set up dynamic scaling for your application. This will help you maintain application performance, improve application availability and reduce costs. This metric is integrated with Auto Scaling through a new type of scaling policy called target tracking scaling policies where you select this metric as a load metric for your application, set the target value, and Auto Scaling adjusts the number of EC2 instances in your Auto Scaling group as needed to maintain that target value. For example, you can configure target tracking scaling policy for your Auto Scaling Group to keep RequestCountPerTarget at 1000 for your webserver fleet. From there, Auto Scaling launches or terminates EC2 instances as required to keep RequestCountPerTarget at 1000. Ans. D

D. Use a target tracking scaling policy based on the ALB's RequestCountPerTarget metric

Ans D. Use a target tracking scaling policy based on the ALB's RequestCountPerTarget metric. "We strongly recommend that you use a target tracking scaling policy to scale on a metric like average CPU utilization or the RequestCountPerTarget metric from the Application Load Balancer. " https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-scaling-simple-step.html

Whynot C?: 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 and from the load balancer to targets. Who answers the question exactly and easily

looks like C : https://aws.amazon.com/about-aws/whats-new/2017/07/application-load-balancer-adds-support-for-new-requestcountpertarget-cloudwatch-metric/

D. Use a target tracking scaling policy based on the ALB's RequestCountPerTarget metric https://aws.amazon.com/about-aws/whats-new/2017/07/application-load-balancer-adds-support-for-new-requestcountpertarget-cloudwatch-metric/