Examkin

Soru

Zorluk: OrtaCloudWatch Metrics and Alarms

An administrator is troubleshooting a CloudWatch alarm configured to monitor the `DiskReadBytes` metric of an Amazon EC2 instance. The alarm has a period of 6060 seconds, an evaluation period of 11, and is set to transition to the `ALARM` state when disk read activity exceeds a specific threshold. The administrator notes that the alarm regularly transitions to the `INSUFFICIENT_DATA` state and fails to trigger during brief periods of high disk reads. The EC2 instance is currently using the default monitoring configuration.

Which action will resolve this issue while maintaining the 60-second60\text{-second} alarm evaluation frequency?

  1. Turn on detailed monitoring for the EC2 instance.Cevap
  2. B
    Increase the alarm period to 55 minutes to match the default metric publishing frequency.
  3. C
    Create an Amazon EventBridge rule that triggers an AWS Systems Manager Automation runbook to poll the disk metrics at 1-minute1\text{-minute} intervals.
  4. D
    Configure an Auto Scaling group cooldown period of 6060 seconds for the instance to force CloudWatch to collect metrics more frequently.

Cevap

Turn on detailed monitoring for the EC2 instance.
The correct option is to turn on detailed monitoring for the EC2 instance. By default, Amazon EC2 sends metric data (such as CPU, disk, and network) to CloudWatch at 5-minute5\text{-minute} intervals (standard monitoring). To run an alarm with a 60-second60\text{-second} period without encountering missing data, detailed monitoring must be enabled to change the metric resolution to 1-minute1\text{-minute} intervals.

Adım Adım Çözüm

1
Analyze the existing monitoring configuration and alarm settings.
The alarm is configured with a period of 6060 seconds, but the EC2 instance is using default (standard) monitoring, which publishes metrics only every 55 minutes.
This mismatch causes the alarm to evaluate periods that contain no data, resulting in frequent transitions to the `INSUFFICIENT_DATA` state.
2
Identify the requirement to maintain a 60-second60\text{-second} evaluation frequency.
Changing the alarm period to 55 minutes is ruled out because the administrator wants to keep the 60-second60\text{-second} detection window.
A 1-minute1\text{-minute} metric resolution is required to support a 60-second60\text{-second} alarm period.
3
Select the configuration change that enables 1-minute1\text{-minute} metric resolution.
Enabling detailed monitoring on the EC2 instance publishes metric data to CloudWatch every minute.
This provides the required data points for the 60-second60\text{-second} alarm period, preventing the alarm from entering the `INSUFFICIENT_DATA` state.

Anahtar Kavram

CloudWatch Standard vs. Detailed Monitoring for EC2 Instances
Bu soruyu puanla

Konular

CloudWatch Metrics and Alarms

Bu konudan daha fazla soru