An automobile sales website stores listings in a database on Amazon RDS. When an automobile is sold, the listing needs to be removed from the website and the data must be sent to multiple target systems. Which design should a solutions architect recommend?

The correct option uses an AWS Lambda function triggered by database updates to send data to an Amazon SQS queue. This is a common and efficient pattern for decoupling data producers (the RDS database via Lambda) from consumers (the target systems). SQS provides a reliable, scalable buffer, ensuring that even if target systems are temporarily unavailable, the data is not lost and can be processed later. Using an SQS FIFO queue is unnecessary here because the order of processing for sold automobile listings is not strictly critical across multiple independent target systems, and standard SQS offers higher throughput. RDS event notifications primarily focus on database operational events (e.g., backup, failover) rather than specific data changes within tables, making them unsuitable for capturing individual listing removals. While SNS can fan out messages, the primary trigger mechanism should be directly tied to the data change in RDS, which Lambda can achieve more directly than relying solely on RDS event notifications for data-level changes.