A company is using Amazon SQS to process background jobs. Occasionally, a message causes the consumer application to crash, and the message is returned to the queue. This creates an infinite loop where the bad message is repeatedly picked up and crashes the application. <br/><br/>How can a solutions architect resolve this issue?

Answer options:

Increase the visibility timeout of the SQS queue.

Configure a Dead-Letter Queue (DLQ) and set the maxReceiveCount on the main queue.

Change the queue type from Standard to FIFO.

Use AWS Lambda to filter out bad messages before they reach the queue.

How to approach this question

Recognize the 'poison pill' scenario and the standard SQS feature used to handle it.

Full Answer

B.Configure a Dead-Letter Queue (DLQ) and set the maxReceiveCount on the main queue.✓ Correct

Configure a Dead-Letter Queue (DLQ) and set the maxReceiveCount on the main queue.

A dead-letter queue (DLQ) is a queue that other (source) queues can target for messages that can't be processed successfully. You set a `maxReceiveCount` on the source queue. If a message is received that many times without being deleted, SQS moves it to the DLQ.

Common mistakes

Thinking visibility timeout solves the problem.

Question 33 All questions Question 35

Practice the full AWS SAA-C03 Practice Exam 4

65 questions · hints · full answers · grading

More questions from this exam

Q01A company has multiple AWS accounts in an AWS Organizations organization. The security team wants...Medium Q02An application running on Amazon EC2 instances needs to access an Amazon DynamoDB table. Both res...Easy Q03A company is designing a web application that will be hosted on AWS. The application will use an ...Medium Q04A company is building a mobile app that requires users to authenticate using their social media a...Hard Q05A solutions architect is designing a VPC for a three-tier web application. The database tier must...Medium

View all 65 questions →