A Company Is Re-Architecting a Strongly Coupled Application to Be

Multiple Choice

A company is Re-architecting a strongly coupled application to be loosely coupled. Previously the application used a request/response pattern to communicate between tiers. The company plans to use Amazon Simple Queue Service (Amazon SQS) to achieve decoupling requirements. The initial design contains one queue for requests and one for responses. However, this approach is not processing all the messages as the application scales. What should a solutions architect do to resolve this issue?

A) Configure a dead-letter queue on the ReceiveMessage API action of the SQS queue.
B) Configure a FIFO queue, and use the message deduplication ID and message group ID.
C) Create a temporary queue, with the Temporary Queue Client to receive each response message.
D) Create a queue for each request and response on startup for each producer, and use a correlation ID message attribute.