Examkin

Soru

Zorluk: OrtaCloudWatch Metrics and Alarms

A SysOps Administrator is managing a production application on Amazon EC2 instances. The instances are running with default monitoring enabled. The administrator configures an Amazon CloudWatch alarm to monitor the CPUUtilization metric of the instances. The alarm is configured with a period of 60 seconds and an evaluation period of 3 consecutive periods. However, the administrator notices that the alarm remains in the INSUFFICIENT_DATA state even when the instances are under high load. Which two actions should the administrator take to resolve this issue and allow the alarm to transition to the ALARM state correctly? (Select TWO.)

  1. Enable detailed monitoring on the EC2 instances.Cevap
  2. Modify the CloudWatch alarm configuration to use a period of 300 seconds (5 minutes) instead of 60 seconds.Cevap
  3. C
    Create an Amazon EventBridge rule that triggers a target to pull CPU metrics from the instances every 60 seconds.
  4. D
    Increase the Auto Scaling group cooldown period to ensure that the metrics have sufficient time to populate.
  5. E
    Configure a custom CloudWatch metric filter to aggregate hypervisor log data at 1-minute intervals.

Cevap

The administrator should enable detailed monitoring on the EC2 instances, or modify the CloudWatch alarm configuration to use a period of 300 seconds (5 minutes).
To resolve the INSUFFICIENT_DATA state, the alarm period must align with the metric reporting frequency. Standard monitoring for EC2 publishes metrics every 5 minutes (300 seconds), whereas detailed monitoring publishes them every 1 minute (60 seconds). Therefore, the administrator must either enable detailed monitoring to provide 1-minute metrics or change the alarm period to 5 minutes to match standard monitoring.

Adım Adım Çözüm

1
Identify that standard EC2 monitoring delivers metrics to CloudWatch every 5 minutes.
Understanding that a 60-second alarm period will lack data points under default settings.
Aligning data resolution with the alarm evaluation period is necessary to prevent the INSUFFICIENT_DATA state.
2
Determine the available resolutions to match the metric delivery interval with the alarm period.
Two valid paths: either increase metric delivery frequency or decrease alarm evaluation frequency.
This resolves the lack of data points during the alarm's evaluation window.
3
Select the configurations that achieve these paths.
Enabling detailed monitoring (increases metric delivery to 1-minute intervals) or changing the alarm period to 300 seconds (decreases evaluation frequency to match the 5-minute standard monitoring).
These are the standard, non-disruptive ways to align metric frequency and alarm duration.

Anahtar Kavram

CloudWatch EC2 monitoring intervals (standard vs. detailed) and their alignment with alarm evaluation periods.
Tahmini Süre:2m 0s
Bu soruyu puanla

Konular

CloudWatch Metrics and Alarms

Bu konudan daha fazla soru