You want to centralize failed message handling by sending failed messages from multiple SQS queues to a single Dead Letter Queue. What is the recommended approach?

hard📝 Best Practice Q8 of 15

AWS - SNS and SQS

ACreate separate DLQs for each source queue and aggregate messages later via Lambda

BConfigure each source queue with the same DLQ ARN and ensure permissions allow all queues to send messages to the DLQ

CUse SNS topics instead of DLQs for centralized failure handling

DSet maxReceiveCount to zero on all source queues to force immediate DLQ routing

Step-by-Step Solution

Solution:

Step 1: Understand DLQ sharing
Multiple SQS queues can share a single DLQ by configuring the same DLQ ARN in their RedrivePolicy.
Step 2: Permissions
Ensure the DLQ policy allows all source queues to send messages to it.
Step 3: Avoid incorrect approaches
Separate DLQs complicate monitoring; SNS is not a DLQ; maxReceiveCount zero is invalid.
Final Answer:
Configure each source queue with the same DLQ ARN and ensure permissions allow all queues to send messages to the DLQ -> Option B
Quick Check:
Use same DLQ ARN with proper permissions for centralization [OK]

Quick Trick: Use same DLQ ARN and permissions for multiple queues [OK]

Common Mistakes:

MISTAKES

Creating separate DLQs unnecessarily
Using SNS instead of DLQ for failed messages
Setting invalid maxReceiveCount values

Master "SNS and SQS" in AWS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More AWS Quizzes

You want to centralize failed message handling by sending failed messages from multiple SQS queues to a single Dead Letter Queue. What is the recommended approach?

Step 1: Understand DLQ sharing

Step 2: Permissions

Step 3: Avoid incorrect approaches

Final Answer:

Quick Check:

Want More Practice?