Examkin

Question

Difficulty: HardCloudWatch Metrics and Alarms

A SysOps Administrator is tasked with setting up automated remediation for a critical application running on a fleet of Amazon EC2 instances. The administrator configures an Amazon CloudWatch alarm on the `CPUUtilization` metric to trigger when the CPU usage exceeds 80%80\% for 33 consecutive periods of 11 minute. The remediation workflow must trigger an AWS Systems Manager (SSM) Automation runbook to collect application logs and reboot the instances. Currently, standard monitoring is enabled on the EC2 instances. During testing, the alarm remains in the `INSUFFICIENT_DATA` state even when CPU utilization is verified to be at 95%95\% for over 1010 minutes, and the remediation workflow fails to run.

Which combination of actions will resolve this issue and enable the automated remediation workflow to run successfully?

  1. A
    Enable detailed monitoring on the EC2 instances. Configure the CloudWatch alarm action to directly invoke the Systems Manager Automation runbook.
  2. Enable detailed monitoring on the EC2 instances. Configure an Amazon EventBridge rule that detects the CloudWatch alarm state change and targets the Systems Manager Automation runbook.Answer
  3. C
    Keep standard monitoring enabled on the EC2 instances. Configure an Amazon EventBridge rule that detects the CloudWatch alarm state change and targets the Systems Manager Automation runbook.
  4. D
    Enable detailed monitoring on the EC2 instances. Configure the CloudWatch alarm to send a notification to an Amazon Simple Notification Service (Amazon SNS) topic, and configure the SNS topic to directly target the Systems Manager Automation runbook.

Answer

Enable detailed monitoring on the EC2 instances, and configure an Amazon EventBridge rule that detects the CloudWatch alarm state change to target the Systems Manager Automation runbook.
The correct solution requires enabling detailed monitoring on the EC2 instances to publish metric data at 11-minute intervals, resolving the `INSUFFICIENT_DATA` status. Additionally, an Amazon EventBridge rule must be configured to catch the alarm state transition and trigger the Systems Manager Automation runbook, since CloudWatch alarms cannot invoke Systems Manager Automation directly.

Step-by-Step Solution

1
Analyze the metric reporting interval requirement.
Standard monitoring publishes CPU utilization metrics every 55 minutes, which cannot satisfy a 11-minute alarm evaluation period.
To resolve the `INSUFFICIENT_DATA` state for a 11-minute alarm period, detailed monitoring (11-minute interval) must be enabled on the EC2 instances.
2
Analyze the remediation action target capability.
CloudWatch alarms cannot directly target Systems Manager Automation runbooks.
An Amazon EventBridge rule must be created to intercept the CloudWatch alarm state change event and route it to the Systems Manager Automation runbook.

Key Concept

CloudWatch alarm evaluation intervals require matching metric granularity, and Systems Manager Automation integrations rely on Amazon EventBridge for event-driven orchestration.
Estimated Time:2m 0s
Rate this question

Topics

CloudWatch Metrics and Alarms

More questions from this topic