A developer is monitoring an application that runs on an Amazon EC2 instance. The developer has configured a custom Amazon CloudWatch metric with data granularity of 1 second. If any issues occur, the

Question

Options

• AConfigure a high-resolution CloudWatch alarm.
• BSet up a custom CloudWatch dashboard.
• CUse Amazon CloudWatch Logs Insights.
• DChange to a default CloudWatch metric.

• A
  81% (42)
• B
  2% (1)
• C
  12% (6)
• D
  6% (3)

Explanation

Option A is correct because high-resolution CloudWatch alarms are specifically designed to trigger on custom metrics with 1-second granularity, and they can evaluate and alert as frequently as every 10 seconds - well within the 30-second notification requirement when paired with SNS.

Why the distractors are wrong:

• B (Custom Dashboard): Dashboards are for visualization only - they display metrics but cannot trigger alerts or send notifications.
• C (CloudWatch Logs Insights): This is a query tool for analyzing log data, not a mechanism for real-time alerting on custom metrics.
• D (Default metric): Default (standard-resolution) CloudWatch metrics have a minimum granularity of 1 minute, which would make a 30-second alert window impossible.

Memory tip: Think "high-resolution = high urgency." Whenever an exam question mentions sub-minute custom metrics (1s, 5s, 10s) combined with a tight alerting window, high-resolution alarms are always the answer. The key phrase to watch for is "1-second granularity" - that immediately rules out standard metrics and points to high-resolution alarms.

No community discussion yet for this question.