exam questions

Exam AWS-SysOps All Questions

View all questions & answers for the AWS-SysOps exam

Exam AWS-SysOps topic 1 question 795 discussion

Exam question from Amazon's AWS-SysOps
Question #: 795
Topic #: 1
[All AWS-SysOps Questions]

An application is running on Amazon EC2 instances behind an Application Load Balancer (ALB). The instances are configured in an Amazon EC2 Auto Scaling group. A SysOps Administrator must configure the application to scale based on the number of incoming requests.
Which solution accomplishes this with the LEAST amount of effort?

  • A. Use a simple scaling policy based on a custom metric that measures the average active requests of all EC2 instances
  • B. Use a simple scaling policy based on the Auto Scaling group GroupDesiredCapacity metric
  • C. Use a target tracking scaling policy based on the ALB's ActiveConnectionCount metric
  • D. Use a target tracking scaling policy based on the ALB's RequestCountPerTarget metric
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
kung07
Highly Voted 2 years, 9 months ago
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
upvoted 29 times
AWSum1
2 years, 8 months ago
Thanks for this link. Great explanation
upvoted 1 times
...
AWS_Noob
2 years, 8 months ago
Awesome info and straight to the point
upvoted 1 times
...
...
albert_kuo
Most Recent 11 months, 3 weeks ago
Selected Answer: D
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.
upvoted 1 times
...
gulu73
1 year, 5 months ago
Selected Answer: D
option D
upvoted 1 times
...
RicardoD
2 years, 8 months ago
D is the answer
upvoted 1 times
...
abhishek_m_86
2 years, 8 months ago
D. Use a target tracking scaling policy based on the ALB's RequestCountPerTarget metric : Seems correct
upvoted 3 times
...
jackdryan
2 years, 8 months ago
I'll go with D
upvoted 2 times
...
trulyrajiv
2 years, 8 months ago
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
upvoted 2 times
...
MFDOOM
2 years, 8 months ago
D. Use a target tracking scaling policy based on the ALB's RequestCountPerTarget metric
upvoted 2 times
...
gilbertlelancelo
2 years, 8 months ago
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
upvoted 2 times
...
MegatonN
2 years, 8 months ago
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
upvoted 3 times
...
rewiga
2 years, 8 months ago
looks like C : https://aws.amazon.com/about-aws/whats-new/2017/07/application-load-balancer-adds-support-for-new-requestcountpertarget-cloudwatch-metric/
upvoted 2 times
rewiga
2 years, 8 months ago
Sorry i mean D
upvoted 2 times
...
...
nicat
2 years, 9 months ago
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/
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...