DVA-C02 · Question #613
A company created an application to consume and process data. The application uses Amazon SQS and AWS Lambda functions. The application is currently working as expected, but it occasionally receives s
The correct answer is B. Create a new SQS queue. Set the new queue as a dead-letter queue for the application queue.. Using a dead-letter queue (DLQ) with Amazon SQS is the most operationally efficient solution for handling unprocessable messages. Amazon SQS Dead-Letter Queue: A DLQ is used to capture messages that fail processing after a specified number of attempts. Allows the application to c
Question
A company created an application to consume and process data. The application uses Amazon SQS and AWS Lambda functions. The application is currently working as expected, but it occasionally receives several messages that it cannot process properly. The company needs to clear these messages to prevent the queue from becoming blocked. A developer must implement a solution that makes queue processing always operational. The solution must give the company the ability to defer the messages with errors and save these messages for further analysis. What is the MOST operationally efficient solution that meets these requirements?
Options
- AConfigure Amazon CloudWatch Logs to save the error messages to a separate log stream.
- BCreate a new SQS queue. Set the new queue as a dead-letter queue for the application queue.
- CChange the SQS queue to a FIFO queue. Configure the message retention period to 0 seconds.
- DConfigure an Amazon CloudWatch alarm for Lambda function errors. Publish messages to an
How the community answered
(30 responses)- A3% (1)
- B70% (21)
- C7% (2)
- D20% (6)
Explanation
Using a dead-letter queue (DLQ) with Amazon SQS is the most operationally efficient solution for handling unprocessable messages. Amazon SQS Dead-Letter Queue: A DLQ is used to capture messages that fail processing after a specified number of attempts. Allows the application to continue processing other messages without being blocked. Messages in the DLQ can be analyzed later for debugging and resolution. Operational Efficiency: Automatically defers messages with errors, ensuring the queue is not Analysis Ready: Messages in the DLQ can be inspected to identify recurring issues. Scalable: Works seamlessly with Lambda and SQS at scale.
Community Discussion
No community discussion yet for this question.