DEA-C01 · Question #296
An ecommerce company uses AWS Glue ETL to process and analyze orders. The company wants to build an extract, transform, and load (ETL) pipeline that processes placed, shipped, delivered, and…
The correct answer is A. Configure a dead-letter queue in EventBridge Scheduler to store failed events. Analyze the failed. Configuring a dead-letter queue for EventBridge Scheduler captures the events that could not be delivered to the target along with the failure context. Reviewing the failed canceled-order events in the DLQ provides the most direct way to identify why the invocations are failing…
Question
An ecommerce company uses AWS Glue ETL to process and analyze orders. The company wants to build an extract, transform, and load (ETL) pipeline that processes placed, shipped, delivered, and canceled orders differently. The company integrates the order processing system with Amazon EventBridge. The company configures EventBridge Scheduler rules for each order status to invoke different AWS Glue workflows. When the company examines Amazon CloudWatch metrics for the workflow, the company notices that the FailedInvocations metric shows a high value for canceled orders. The company must determine the cause of the failed invocations. Which solution will meet this requirement?
Options
- AConfigure a dead-letter queue in EventBridge Scheduler to store failed events. Analyze the failed
- BUse the archive and replay features in EventBridge Scheduler to investigate the issue.
- CChange the retry policy in EventBridge Scheduler to reduce the value for maximum retries.
- DChange the retry policy in EventBridge Scheduler to increase the value for maximum age of
How the community answered
(51 responses)- A73% (37)
- B10% (5)
- C4% (2)
- D14% (7)
Explanation
Configuring a dead-letter queue for EventBridge Scheduler captures the events that could not be delivered to the target along with the failure context. Reviewing the failed canceled-order events in the DLQ provides the most direct way to identify why the invocations are failing (for example, payload issues, permission errors, or target configuration problems) without changing retry
Topics
Community Discussion
No community discussion yet for this question.