A company has 10 Amazon EC2 instances in its production account. A SysOps administrator must ensure that email notifications are sent to administrators each time there is an EC2 instance state…

Question

Options

• AConfigure an Amazon Route 53 simple routing policy that publishes a message to an Amazon
• BConfigure an Amazon Route 53 simple routing policy that publishes a message to an Amazon
• CCreate an Amazon EventBridge (Amazon CloudWatch Events) rule that publishes a message to
• DCreate an Amazon EventBridge (Amazon CloudWatch Events) rule that publishes a message to

• A
  2% (1)
• B
  5% (2)
• C
  93% (40)

Explanation

Option C is correct because Amazon EventBridge (formerly CloudWatch Events) is the purpose-built AWS service for detecting and reacting to infrastructure state changes. When an EC2 instance changes state (e.g., running → stopped), EventBridge captures that event automatically. The rule can then publish to an Amazon SNS topic, which sends email notifications to subscribed administrators - no polling or custom code required.

Why A and B are wrong: Amazon Route 53 is a DNS and traffic routing service. It has no capability to monitor EC2 instance state changes or trigger notifications based on infrastructure events. These choices mix unrelated services.

Why D is wrong: Although D also uses EventBridge (the right starting point), the answer choices are truncated here - typically D differs by targeting the wrong downstream service (e.g., SQS instead of SNS, or Lambda without email delivery), making it unsuitable for direct email notification without additional configuration.

Memory tip: Think "Event → EventBridge → SNS → Email" as the standard AWS notification pipeline. Whenever a question mentions reacting to AWS service state changes plus email alerts, the pattern is almost always EventBridge rule → SNS topic with email subscription. Route 53 = DNS only; never a monitoring tool.

No community discussion yet for this question.