Which service is appropriate when you want to accumulate messages in a queue between multiple AWS services or applications and process them asynchronously?

Explanation

Amazon SQS is a message queue service that holds messages in a queue until the processing side retrieves them. It is used for asynchronous processing and loose coupling.

Per-choice explanations

Practical Use

Amazon SQS (Simple Queue Service) is a fully managed message queue service provided by AWS. The sender (producer) places messages into the SQS queue, where they are held temporarily, and the receiver (consumer) retrieves and processes them at its own pace. The sender and receiver do not need to be running at the same time, and processing can continue even if one side is down, so SQS serves as the foundation for loosely coupling components. On the exam, the typical question asks which service is appropriate when you want to accumulate messages in a queue between multiple AWS services or applications and process them asynchronously, or when you want to absorb processing spikes and decouple components. Amazon SQS is the answer. Distractors that frequently appear include Amazon SNS (publish/subscribe notifications), AWS CloudTrail (API activity history), and Amazon Route 53 (DNS). SNS is for pushing the same message to multiple subscribers, which is a different role from SQS, which holds messages in a queue and processes them in order. In practice, SQS is often used with EC2 worker fleets or AWS Lambda behind the queue to process asynchronous jobs. There are two types: Standard queues and FIFO queues. Choose FIFO when ordering and deduplication are required. CLF-C02 tends to test the division of roles between queue and pub/sub, comparing SQS and SNS. From SAA-C03 and above, message visibility timeout, dead-letter queues, and the SNS plus SQS fan-out pattern (SNS to multiple SQS queues) are also tested.