A SysOps Administrator is configuring an Amazon CloudWatch alarm to monitor the CPU utilization of a standalone Amazon EC2 instance. The administrator wants the alarm to evaluate metrics at 1-minute intervals. However, the alarm remains in the INSUFFICIENT_DATA state because the CPU metric is only being reported every 5 minutes. Which actions must the administrator take to resolve this issue? (Select TWO.)
- Enable detailed monitoring on the EC2 instance.Cevap
- Configure the CloudWatch alarm with a period of 60 seconds.Cevap
- CEnable high-resolution metrics on the EC2 instance.
- DCreate an Amazon EventBridge rule to poll the EC2 instance CPU metrics every 60 seconds.
- EModify the EC2 Auto Scaling group cooldown period to 60 seconds.
Cevap
Enable detailed monitoring on the EC2 instance and configure the CloudWatch alarm with a period of 60 seconds.
To resolve the insufficient data issue and alarm at a 1-minute frequency, standard EC2 monitoring (5-minute interval) must be upgraded to detailed monitoring, which publishes metrics every 1 minute. Additionally, the CloudWatch alarm itself must be configured with a 60-second evaluation period to match the metric publishing rate.
Adım Adım Çözüm
Anahtar Kavram
By default, EC2 instances report metrics at a 5-minute frequency (standard monitoring). To evaluate metrics at a 1-minute resolution, detailed monitoring must be enabled on the instance, and the CloudWatch alarm's evaluation period must be configured to 60 seconds.