SAP-C02 · Question #71
A company has implemented an ordering system using an event-dnven architecture. Dunng initial testing, the system stopped processing orders Further tog analysis revealed that one order message in an…
The correct answer is D. Configure a new SOS standard queue as a dead-letter queue to isolate the faulty messages. You need a dead-letter queue with a type that matches the queue. So a DLQ for a standard queue must 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-dnven architecture. Dunng initial testing, the system stopped processing orders Further tog analysis revealed that one order message in an Amazon Simple Queue Service (Amazon SOS) 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 SOS FIFO queue as a dead-letter queue to isolate the faulty messages
- DConfigure a new SOS standard queue as a dead-letter queue to isolate the faulty messages.
How the community answered
(35 responses)- A3% (1)
- B9% (3)
- C17% (6)
- D71% (25)
Explanation
You need a dead-letter queue with a type that matches the queue. So a DLQ for a standard queue must 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.