You configured a DLQ with maxReceiveCount set to 5, but messages are not moving to the DLQ after 5 failed processing attempts. What is the most likely cause?

medium📝 Debug Q14 of 15

AWS - SNS and SQS

AmaxReceiveCount must be set to 1 for DLQ to work

BThe DLQ ARN is invalid but messages still move to DLQ

CThe RedrivePolicy is missing or incorrectly attached to the main queue

DMessages are deleted automatically after 3 failures regardless of DLQ

Step-by-Step Solution

Solution:

Step 1: Check RedrivePolicy attachment
If RedrivePolicy is missing or not attached properly, messages won't move to DLQ.
Step 2: Validate other options
Invalid ARN would cause errors, maxReceiveCount can be any positive number, and messages are not deleted automatically without DLQ.
Final Answer:
The RedrivePolicy is missing or incorrectly attached to the main queue -> Option C
Quick Check:
DLQ requires correct RedrivePolicy attachment [OK]

Quick Trick: Verify RedrivePolicy is attached to main queue [OK]

Common Mistakes:

MISTAKES

Ignoring RedrivePolicy attachment
Assuming invalid ARN still works
Believing maxReceiveCount must be 1

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 configured a DLQ with maxReceiveCount set to 5, but messages are not moving to the DLQ after 5 failed processing attempts. What is the most likely cause?

Step 1: Check RedrivePolicy attachment

Step 2: Validate other options

Final Answer:

Quick Check:

Want More Practice?