An application hosted on Amazon EC2 instances in an Auto Scaling group (ASG) experiences sudden spikes in traffic. The ASG is configured to scale out using a step scaling policy based on the average CPU utilization of the instances. Currently, the ASG takes up to minutes to respond to a traffic spike, which leads to degraded application performance. A SysOps administrator needs to configure the ASG to scale out more quickly during these spikes.
Which two changes should the SysOps administrator make to reduce the time it takes for the ASG to scale out? (Select TWO.)
- Enable detailed monitoring in the launch template used by the Auto Scaling group.Cevap
- Decrease the evaluation periods for the CloudWatch alarm that triggers the scaling policy.Cevap
- CIncrease the scaling cooldown period on the step scaling policy.
- DEnable Auto Scaling group metrics collection in the Amazon EC2 console.
- EConfigure an Amazon EventBridge rule that detects high CPU utilization to trigger an AWS Systems Manager Automation runbook that scales the ASG.
Cevap
The correct answers are enabling detailed monitoring in the launch template and decreasing the evaluation periods for the CloudWatch alarm.
To minimize the delay in scaling out during traffic spikes, the SysOps administrator must reduce both the time it takes for metrics to be reported and the time it takes for the alarm to trigger. Enabling detailed monitoring in the launch template changes the CPU utilization reporting interval from minutes to minute. Decreasing the evaluation periods for the CloudWatch alarm ensures that the alarm transitions to the ALARM state quickly when the threshold is crossed, rather than waiting for multiple metric intervals to pass.
Adım Adım Çözüm
Anahtar Kavram
Auto Scaling responsiveness optimization using metric resolution and alarm evaluation settings
Tahmini Süre:1m 30s