Examkin

Question

Difficulty: MediumCloudWatch Metrics and Alarms

A company runs a latency-sensitive application on a fleet of Amazon EC2 instances. A SysOps Administrator is tasked with configuring a CloudWatch alarm to detect when the CPUUtilization metric exceeds 85%85\% for 33 consecutive 1-minute1\text{-minute} evaluation periods. If the threshold is breached, the administrator must configure a notification to be sent to an Amazon SNS topic. Currently, the instances are reporting metrics at the default interval.

Which configurations are required to meet these requirements? (Select TWO.)

  1. Activate detailed monitoring on the EC2 instances to report metrics at 1-minute1\text{-minute} intervals.Answer
  2. Configure a CloudWatch alarm with a period of 60 seconds60\text{ seconds} and set the evaluation periods to 33.Answer
  3. C
    Configure the CloudWatch alarm with a period of 60 seconds60\text{ seconds} while keeping the default standard monitoring interval active for the instances.
  4. D
    Create an Amazon EventBridge rule that queries the CPUUtilization metric at 1-minute1\text{-minute} intervals and sends notifications to the SNS topic.
  5. E
    Set the Auto Scaling group cooldown period to 60 seconds60\text{ seconds} and attach an SNS notification action to the scaling policy.

Answer

To monitor CPU utilization at 1-minute intervals and send SNS notifications, the administrator must activate detailed monitoring on the EC2 instances and configure the CloudWatch alarm with a period of 60 seconds and an evaluation period of 3.
To monitor and alert on a metric with 1-minute granularity, detailed monitoring must be enabled on the EC2 instances because the default standard monitoring reports CPU utilization metrics at 5-minute intervals. Additionally, the CloudWatch alarm must be configured with a period of 60 seconds and an evaluation period of 3 to check three consecutive 1-minute data points before triggering the alarm.

Step-by-Step Solution

1
Enable detailed monitoring.
EC2 instances publish metrics to CloudWatch every 1 minute instead of the default 5 minutes.
Standard monitoring granularity is 5 minutes, which does not provide the 1-minute data resolution required for the alarm.
2
Configure CloudWatch alarm period and evaluation settings.
The alarm is configured with a period of 60 seconds and evaluation periods set to 3.
This setup allows CloudWatch to evaluate three consecutive 1-minute data points and transition the alarm to the ALARM state if the threshold is breached.

Key Concept

CloudWatch detailed monitoring provides 1-minute resolution metrics for EC2 instances, which is necessary for configuring alarms with periods shorter than 5 minutes.
Estimated Time:1m 30s
Rate this question

Topics

CloudWatch Metrics and Alarms

More questions from this topic