SOA-C02 · Question #695
A company's APIs are not receiving all their expected events. The company has hundreds of Amazon EventBridge rules configured and no dead-letter queues for failed event delivery. A SysOps…
The correct answer is D. Create an Amazon CloudWatch alarm that uses the FailedInvocations metric for EventBridge. Amazon EventBridge emits a built-in CloudWatch metric called FailedInvocations (in the AWS/EventBridge namespace), which tracks when a rule’s target invocation fails. You can create a single CloudWatch alarm on that metric (optionally aggregating across all rules by omitting…
Question
A company’s APIs are not receiving all their expected events. The company has hundreds of Amazon EventBridge rules configured and no dead-letter queues for failed event delivery. A SysOps administrator must implement a solution that notifies an Amazon Simple Notification Service (Amazon SNS) topic when EventBridge rules are broken. Which solution will meet this requirement?
Options
- AUse the EventBridge replay capability to replay FailedInvocations events. Configure Amazon
- BCreate an EventBridge pipe that has a source of AllEvents. Set filtering in the pipe for
- CCreate an EventBridge rule that forwards failed events to the SNS topic. Use message filtering in
- DCreate an Amazon CloudWatch alarm that uses the FailedInvocations metric for EventBridge.
How the community answered
(37 responses)- A11% (4)
- B5% (2)
- C3% (1)
- D81% (30)
Explanation
Amazon EventBridge emits a built-in CloudWatch metric called FailedInvocations (in the AWS/EventBridge namespace), which tracks when a rule’s target invocation fails. You can create a single CloudWatch alarm on that metric (optionally aggregating across all rules by omitting the RuleName dimension) and point the alarm’s notification action to the SNS topic. This approach requires no custom event buses, no piping configurations, and scales automatically as you add
Topics
Community Discussion
No community discussion yet for this question.