Examkin

Question

Difficulty: HardCloudWatch Metrics and Alarms

A SysOps Administrator is configuring an automated remediation workflow for an application running on a standalone Amazon EC2 instance. The administrator wants to execute a custom AWS Systems Manager (SSM) Automation document to reboot the instance when the `CPUUtilization` metric exceeds 80%80\% for 33 consecutive 11-minute periods. Currently, default monitoring is enabled on the instance. During testing, the alarm remains in the `INSUFFICIENT_DATA` state and fails to trigger the remediation workflow.

Which of the following actions should the administrator take to resolve this issue and execute the remediation workflow? (Select TWO.)

  1. Enable detailed monitoring on the EC2 instance.Answer
  2. Create an Amazon EventBridge rule that is triggered by the CloudWatch alarm state change to ALARM, and set the SSM Automation document as the target.Answer
  3. C
    Change the CloudWatch alarm evaluation period to 55 minutes, and add the SSM Automation document directly as an alarm action.
  4. D
    Configure the CloudWatch alarm to send a message to an Amazon Simple Queue Service (Amazon SQS) queue, and configure the queue to directly invoke the SSM Automation document.
  5. E
    Modify the Auto Scaling group cooldown period to allow the alarm to execute the SSM Automation document.

Answer

To resolve the issues, the administrator must enable detailed monitoring on the EC2 instance to receive metric updates every minute, and construct an Amazon EventBridge rule that intercepts the CloudWatch alarm state change to trigger the Systems Manager Automation document.
To resolve the metric data issue, detailed monitoring must be enabled on the EC2 instance. Detailed monitoring changes the data aggregation frequency from 55 minutes to 11 minute, satisfying the alarm's requirement for consecutive 11-minute evaluation periods. To resolve the execution failure, an Amazon EventBridge rule must be created to intercept the CloudWatch alarm transition to the ALARM state and trigger the Systems Manager Automation document, as CloudWatch alarms cannot directly invoke Automation runbooks.

Step-by-Step Solution

1
Analyze the metric collection frequency configuration.
Default (standard) EC2 monitoring collects metrics at 55-minute intervals. Because the alarm requires three consecutive 11-minute evaluation periods, it lacks sufficient datapoints and remains in the INSUFFICIENT_DATA state.
Detailed monitoring must be enabled on the EC2 instance to supply CloudWatch with metrics at the required 11-minute frequency.
2
Determine the correct target configuration for the remediation workflow.
CloudWatch alarms cannot natively invoke Systems Manager Automation documents directly as an alarm action.
An Amazon EventBridge rule must be created to detect the alarm state change and route the execution request to the Systems Manager Automation document target.

Key Concept

CloudWatch detailed monitoring configuration and EventBridge-based automated remediation.
Rate this question

Topics

CloudWatch Metrics and Alarms

More questions from this topic