SAA-C03 Question #120: Real Exam Question with Answer & Explanation

Question

A company runs a payment processing system in the AWS Cloud Sometimes when a payment fails because of insufficient funds or technical issues, users attempt to resubmit the payment. Sometimes payment resubmissions invoke multiple payment messages for the same payment ID. A solutions architect needs to ensure that the payment processing system receives payment messages that have the same payment ID sequentially, according to when the messages were generated. The processing system must process the messages in the order in which the messages are received. The solution must retain all payment messages for 10 days for analytics. Which solutions will meet these requirements? (Select TWO.)

Options

• AWrite the payment messages to an Amazon DynamoDB table that uses the payment ID as the
• BWrite the payment messages to an Amazon Kinesis data stream that uses the payment ID as the
• CWrite the payment messages to an Amazon ElastiCache for Memcached cluster that uses the
• DWrite the payment messages to an Amazon Simple Queue Service (Amazon SQS) queue. Set
• EWrite the payment messages to an Amazon Simple Queue Service (Amazon SQS) FIFO queue

Explanation

Both Amazon Kinesis and SQS FIFO queues ensure the sequential processing of messages. By using the payment ID as the partition key in Kinesis or as the message group in the SQS FIFO queue, messages are processed in order. Both solutions also allow for long-term retention (up to 10 days) of messages, making them suitable for this payment processing use case. Option A (DynamoDB): DynamoDB does not guarantee message ordering for real-time Option C (ElastiCache): ElastiCache is for caching, not suitable for sequential message Option D (Standard SQS queue): A standard SQS queue does not guarantee ordering of

No community discussion yet for this question.