SAP-C02 · Question #543
A company has implemented an ordering system using an event-driven architecture. During initial testing, the system stopped processing orders. Further log analysis revealed that one order message in…
The correct answer is D. Configure a new SQS standard queue as a dead-letter queue to isolate the faulty messages. The dead-letter queue of a FIFO queue must also be a FIFO queue. Similarly, the dead-letter queue of a standard queue must also be a standard queue. https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead- letter-queues.html
Question
A company has implemented an ordering system using an event-driven architecture. During initial testing, the system stopped processing orders. Further log analysis revealed that one order message in an Amazon Simple Queue Service (Amazon SQS) standard queue was causing an error on the backend and blocking all subsequent order messages. The visibility timeout of the queue is set to 30 seconds, and the backend processing timeout is set to 10 seconds. A solutions architect needs to analyze faulty order messages and ensure that the system continues to process subsequent messages. Which step should the solutions architect take to meet these requirements?
Options
- AIncrease the backend processing timeout to 30 seconds to match the visibility timeout.
- BReduce the visibility timeout of the queue to automatically remove the faulty message.
- CConfigure a new SQS FIFO queue as a dead-letter queue to isolate the faulty messages.
- DConfigure a new SQS standard queue as a dead-letter queue to isolate the faulty messages.
How the community answered
(41 responses)- A7% (3)
- B5% (2)
- C17% (7)
- D71% (29)
Explanation
The dead-letter queue of a FIFO queue must also be a FIFO queue. Similarly, the dead-letter queue of a standard queue must also be a standard queue. https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-dead- letter-queues.html
Community Discussion
No community discussion yet for this question.