Bird
0
0

A developer set up a Dead Letter Queue but messages are still visible in the main queue after multiple failures. What should be checked first?

medium📝 Debug Q7 of 15
AWS - SNS and SQS
A developer set up a Dead Letter Queue but messages are still visible in the main queue after multiple failures. What should be checked first?
AVerify if maxReceiveCount is configured correctly.
BCheck if the DLQ has enough storage space.
CConfirm if the main queue has encryption enabled.
DEnsure the messages are not too large.
Step-by-Step Solution
Solution:

  1. Step 1: Understand DLQ message move condition

    Messages move to DLQ only after exceeding maxReceiveCount.

  2. Step 2: Check maxReceiveCount configuration

    If maxReceiveCount is missing or set too high, messages remain in main queue despite failures.

  3. Final Answer:

    Verify if maxReceiveCount is configured correctly. -> Option A

  4. Quick Check:

    Incorrect maxReceiveCount = messages stay in main queue [OK]
Quick Trick: maxReceiveCount controls DLQ message transfer [OK]
Common Mistakes:
MISTAKES
  • Checking DLQ storage instead of maxReceiveCount
  • Assuming encryption affects DLQ behavior
  • Focusing on message size unnecessarily

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes
AWS Lambda - Lambda pricing model - Quiz 6medium Auto Scaling - Scheduled scaling - Quiz 2easy Auto Scaling - Launch templates - Quiz 5medium Auto Scaling - Auto Scaling with ELB integration - Quiz 3easy Auto Scaling - Launch templates - Quiz 1easy CloudWatch - Why monitoring matters - Quiz 5medium DynamoDB - Scan vs query performance - Quiz 2easy RDS and Relational Databases - Why managed databases matter - Quiz 12easy RDS and Relational Databases - Multi-AZ deployment for high availability - Quiz 12easy SNS and SQS - Sending and receiving messages - Quiz 2easy