Dead letter queues in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Purpose of Dead Letter Queues in AWS

What is the primary purpose of a Dead Letter Queue (DLQ) in AWS messaging services like SQS or SNS?

A To store messages that failed processing after multiple retries for later analysis or reprocessing.

B To permanently delete messages that cause errors during processing.

C To automatically retry messages indefinitely until they succeed.

D To encrypt messages before sending them to the main queue.

💡 Hint

Think about what happens to messages that cannot be processed successfully.

Dead Letter Queues hold messages that failed processing after a set number of retries, allowing developers to inspect and handle them separately without losing data.

❓ Configuration

intermediate

Configuring a Dead Letter Queue for an SQS Queue

You want to configure an SQS queue to send failed messages to a Dead Letter Queue after 5 failed processing attempts. Which configuration setting must you set on the main queue?

A Enable server-side encryption on the main queue.

B Set the VisibilityTimeout attribute to 5 seconds on the main queue.

C Set the DelaySeconds attribute to 5 on the DLQ.

D Set the RedrivePolicy attribute with maxReceiveCount set to 5 and specify the ARN of the DLQ.

💡 Hint

Look for the setting that controls how many times a message can be received before moving to DLQ.

The RedrivePolicy attribute on the main queue specifies the DLQ ARN and maxReceiveCount, which controls after how many failed receives the message is sent to the DLQ.

❓ Architecture

advanced

Designing a Reliable Message Processing System with DLQ

You are designing a system that processes messages from an SQS queue. To ensure no message is lost and failures are handled gracefully, which architecture pattern involving DLQs is best?

A Use a main SQS queue with a DLQ configured; process messages and on failure, messages move to DLQ for manual or automated reprocessing.

B Use only a DLQ without a main queue to store all messages directly.

C Process messages directly from the DLQ and discard messages from the main queue.

D Use multiple main queues without DLQs and rely on message visibility timeout for retries.

💡 Hint

Consider how to separate failed messages from successfully processed ones.

The best practice is to have a main queue for normal processing and a DLQ to isolate failed messages for later handling, ensuring reliability and no message loss.

❓ service_behavior

advanced

Behavior of Messages in DLQ After Reaching maxReceiveCount

What happens to a message in an SQS main queue when it reaches the maxReceiveCount specified in the RedrivePolicy?

A The message is deleted permanently from the main queue without moving to any other queue.

B The message is moved automatically to the configured Dead Letter Queue and removed from the main queue.

C The message is retried indefinitely in the main queue without moving to DLQ.

D The message is archived in the main queue but remains visible for processing.

💡 Hint

Think about what the RedrivePolicy controls regarding message retries and failures.

When a message's receive count exceeds maxReceiveCount, SQS moves it to the DLQ and removes it from the main queue to prevent infinite retries.

❓ security

expert

Securing Access to Dead Letter Queues in AWS

You want to ensure that only specific AWS Lambda functions can read messages from your SQS Dead Letter Queue. Which is the best way to enforce this access control?

A Use a public access policy on the DLQ to allow all AWS services to read messages.

B Set the DLQ's RedrivePolicy to restrict access to Lambda functions.

C Attach an IAM policy to the Lambda functions allowing sqs:ReceiveMessage and sqs:DeleteMessage on the DLQ ARN, and set a resource-based policy on the DLQ to allow only those Lambda roles.

D Enable server-side encryption on the DLQ and rely on encryption keys to restrict access.

💡 Hint

Consider both IAM roles and resource policies for fine-grained access control.

Combining IAM policies on Lambda roles with resource-based policies on the DLQ ensures only authorized Lambdas can read and delete messages, enforcing strict access control.