Soru

Zorluk: OrtaCloudWatch Metrics and Alarms

A company runs a critical application on a fleet of Amazon EC2 instances. A SysOps Administrator is configuring a CloudWatch alarm to monitor the aggregate CPU utilization of the fleet. The alarm must transition to the ALARM state and send an Amazon SNS notification if the average CPU utilization exceeds 85%85\% for 22 consecutive evaluation periods of 11 minute. The EC2 instances are currently configured with standard monitoring.

Which combination of actions must the SysOps Administrator take to meet these requirements? (Select TWO.)

  1. Enable detailed monitoring on the EC2 instances in the fleet.Cevap
  2. Configure the CloudWatch alarm with a metric period of 11 minute and set both the Evaluation Periods and Datapoints to Alarm to 22.Cevap
  3. C
    Keep standard monitoring enabled and configure the CloudWatch alarm with a metric period of 11 minute, relying on CloudWatch to interpolate the 55-minute metrics.
  4. D
    Create an Amazon EventBridge rule that directly monitors the raw EC2 CPUUtilization metric stream at 11-minute intervals to trigger the SNS notification.
  5. E
    Increase the Auto Scaling group cooldown period to 120120 seconds to prevent CloudWatch from evaluating metrics during instance scaling activities.

Cevap

To achieve this configuration, detailed monitoring must be enabled on the EC2 instances, and the CloudWatch alarm must be configured with a metric period of 11 minute while setting both the Evaluation Periods and Datapoints to Alarm to 22.
To evaluate a metric at 11-minute intervals, the EC2 instances must be configured with detailed monitoring, as standard monitoring only reports metrics at 55-minute intervals. Additionally, the CloudWatch alarm must be configured with a period of 11 minute, and both the Evaluation Periods and Datapoints to Alarm must be set to 22 to ensure that the alarm only triggers when the CPU utilization threshold of 85%85\% is exceeded for 22 consecutive 11-minute periods.

Adım Adım Çözüm

1
Ensure the underlying metrics are published at the required frequency.
Detailed monitoring is enabled on the fleet's EC2 instances, switching the CPU utilization reporting interval from 55 minutes to 11 minute.
Standard monitoring does not provide the 11-minute data points required for the alarm's evaluation period.
2
Configure the threshold evaluation window on the CloudWatch alarm.
The alarm is configured with a period of 11 minute, Evaluation Periods of 22, and Datapoints to Alarm (M out of N) of 22.
This configuration requires 22 out of 22 consecutive data points to exceed the 85%85\% threshold before triggering the alarm.

Anahtar Kavram

CloudWatch detailed monitoring configuration and multi-period alarm evaluation.
Bu soruyu puanla