Add an SQS standard dead-letter queue and a CloudWatch Logs target to the EventBridge rule, and audit activity with CloudTrail

Answer Correct answer: B, C, E — audit events with CloudTrail, add an SQS standard dead-letter queue, and target CloudWatch Logs from the rule.

A company has an event-driven JavaScript application. The application uses decoupled AWS managed services that publish, consume, and route events. During application testing, events are not delivered to the target that is specified by an Amazon EventBridge rule. A DevOps team must provide application testers with additional functionality to view, troubleshoot, and prevent the loss of events without redeployment of the application. Which combination of steps should the DevOps team take to meet these requirements? (Choose three.)

  1. Launch AWS Device Farm with a standard test environment and project to run a specific build of the application.
  2. Create an Amazon S3 bucket. Enable AWS CloudTrail. Create a CloudTrail trail that specifies the S3 bucket as the storage location. Correct Answer
  3. Configure the EventBridge rule to use an Amazon Simple Queue Service (Amazon SQS) standard queue as a dead-letter queue. Correct Answer
  4. Configure the EventBridge rule to use an Amazon Simple Queue Service (Amazon SQS) FIFO queue as a dead-letter queue.
  5. Create a log group in Amazon CloudWatch Logs Specify the log group as an additional target of the EventBridge rule. Correct Answer

Community Votes

BCE
100%

100% of anonymous learners picked answer BCE. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The binding constraint is troubleshooting and preventing loss without touching the application code (B, C, E). A dead-letter queue retains events that failed to deliver so they can be inspected and replayed (C), and a CloudWatch Logs target on the rule gives immediate visibility into the events flowing through it (E). CloudTrail provides the independent audit record of the event activity (B). Option A, AWS Device Farm, is a mobile and web application testing service with no relationship to event delivery. Option D's FIFO dead-letter queue adds ordering and deduplication semantics that are not required and, importantly, an SQS FIFO queue cannot be used as an EventBridge dead-letter queue target.

Testers need to view, troubleshoot, and prevent event loss without redeploying the application. Enabling AWS CloudTrail delivers the event activity to Amazon S3 so testers have an audit trail to inspect after the fact. Configuring the EventBridge rule with an Amazon SQS standard queue as a dead-letter queue captures events that could not be delivered so they are not silently lost, and adding a CloudWatch Logs log group as an additional rule target lets testers view the event flow directly. All three are external to the application, so no redeployment is needed.

Using an SQS FIFO queue as the EventBridge dead-letter queue (D) — EventBridge dead-letter queues must be standard SQS queues; FIFO queues are not supported as dead-letter queue targets, and the ordering semantics are unnecessary here. Launching AWS Device Farm (A) — it is a service for testing mobile and web applications on real devices, entirely unrelated to EventBridge event delivery, and adding it would not help diagnose missing events.

Community Discussion (10 comments)

RajAWSDevOps007 👍 2 Selected: BCE
F is incorrect because it invites an app redeployment with SDK being used to change code base! So BCE are the correct options
jamesf 👍 3 Selected: BCE
Keywords: without redeployment of the application. Option B: Enabling CloudTrail will allow testers to track event activities and interactions with AWS services, aiding in troubleshooting. Option C: Using a standard SQS queue as a DLQ ensures that failed events are captured and can be analyzed or retried. Option E: Adding CloudWatch Logs as a target provides immediate logging of event processing, aiding in real-time monitoring and troubleshooting.
TEC1 👍 2 Selected: CE
I will go with CEF
dalieba 👍 1
CEF, X-ray enables you to debug distributed applications to troubleshoot the root cause of performance issues and errors
noisonnoiton 👍 4 Selected: BCE
without redeployment of the application. B,C,E
tgv 👍 1
---> CEF I thought E its not possible, but --> https://repost.aws/knowledge-center/cloudwatch-log-group-eventbridge
trungtd 👍 1 Selected: CE
C allows you to capture events that could not be delivered to the specified target E capture detailed logs of the events that are processed F end-to-end tracing capabilities B is wrong because while CloudTrail provides logging for AWS API calls, it is not specifically designed for capturing and troubleshooting event flows in EventBridge
siheom 👍 3 Selected: BCE
BCE...
xdkonorek2 👍 1 Selected: CE
CEF C > D - because SQS FIFO is not supported by Dead Letter Queues in event bridge
xdkonorek2 👍 1 Selected: CD
CDF C > D - because SQS FIFO is not supported by Dead Letter Queues in event bridge

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

All three selected steps operate outside the application, satisfying the requirement that testers get new functionality without redeployment. Enabling AWS CloudTrail and pointing a trail at an S3 bucket produces an independent record of the event activity for later inspection (B). Configuring the EventBridge rule to use an SQS standard queue as a dead-letter queue ensures events that could not be delivered to their targets are retained rather than lost, which both prevents loss and gives testers something concrete to inspect (C). Adding a CloudWatch Logs log group as an additional target of the EventBridge rule surfaces the events themselves in a queryable log for live troubleshooting (E).

Why the Other Options Are Wrong

A proposes launching AWS Device Farm with a test project. Device Farm is a service for testing mobile and web applications on physical devices, and it has no relationship to EventBridge event routing, so it cannot help view or troubleshoot undelivered events. D proposes configuring the rule to use an SQS FIFO queue as the dead-letter queue. EventBridge dead-letter queues must be standard SQS queues; FIFO queues are not supported for this purpose, and the deduplication and ordering semantics they introduce are not required by the requirement. A, B, C, and E is not possible since only three may be chosen, and A and D are the two incorrect options. B, C, and E are correct.

Community Comment Notes

Community voted B,C,E (74). Commenters keyed on the phrase 'without redeployment of the application', noting that CloudTrail gives testers the event activity to track, the dead-letter queue retains undelivered events, and the CloudWatch Logs target provides visibility. RajAWSDevOps007 specifically excluded the Device Farm option because it would require application-level changes.

Official Reference

Related Analysis

Practice All DOP-C02 Questions

Access 85 questions with complete answers and detailed explanations.

View Full DOP-C02 Practice Test →

← Back to DOP-C02 Study Guide