AWS Certified Solutions Architect Professional SAP-C02 Practice Question

Publishing the events to an Amazon SQS standard queue meets all three requirements. SQS stores messages redundantly across multiple AZs, so an AZ failure or consumer crash does not cause data loss. Standard queues deliver messages at least once, so the consumer should already be idempotent to tolerate duplicates. By attaching a redrive policy that moves a message to a dead-letter queue after three failed receives, poison messages are automatically isolated without writing additional code.

A FIFO queue with a single message-group ID restricts throughput and still needs a dead-letter queue; it offers features that are unnecessary for this use case. Kinesis Data Streams handles high volume but lacks built-in DLQ support and would require additional consumer logic. Amazon MQ Active/Standby provides durability but does not scale as easily and still requires custom handling for poison messages. Therefore, the SQS standard queue with a redrive policy and multi-AZ consumers is the simplest, most reliable solution.