A SysOps Administrator is configuring an Amazon EC2 Auto Scaling group (ASG) to dynamically scale out. The ASG is currently using standard monitoring. The administrator needs to configure a CloudWatch alarm that will trigger the scale-out policy when the average CPU utilization exceeds for two consecutive 1-minute periods. Which two configurations or actions must the administrator perform to achieve this?
- Enable detailed monitoring in the Auto Scaling group launch template to ensure metric data is available at 1-minute granularityCevap
- Configure the CloudWatch alarm with a period of seconds and evaluation periods of Cevap
- CLeave standard monitoring enabled and configure the CloudWatch alarm with a period of seconds and evaluation periods of
- DConfigure the CloudWatch alarm to trigger the scale-out policy by directly targeting an Amazon Kinesis Data Firehose delivery stream when the alarm state changes
- EConfigure the scaling policy cooldown period to seconds to ensure the scaling policy executes immediately when the alarm triggers
Cevap
To configure the alarm to trigger on two consecutive 1-minute CPU utilization periods, the administrator must enable detailed monitoring on the Auto Scaling group launch template to get 1-minute metric granularity, and configure the CloudWatch alarm with a period of 60 seconds and an evaluation period of 2.
To resolve this requirement, the administrator must ensure that CPU utilization metrics are reported to CloudWatch at 1-minute intervals by enabling detailed monitoring. Then, they must configure the CloudWatch alarm with a period of 60 seconds and an evaluation period of 2 so that it evaluates two consecutive 1-minute datapoints before triggering the scaling policy.
Adım Adım Çözüm
Anahtar Kavram
Enabling detailed monitoring is required to monitor EC2 metrics at 1-minute granularity, and the alarm period and evaluation periods must be configured to match the desired window of observation.