Question 370
A payment API can commit before its response is lost. A client may retry after a timeout. Which protocol-level design prevents duplicate payment side effects?
Explanation
Correct Answer
Timeout creates uncertainty, not definite failure; authoritative status and deduplication protect money-moving transactions.
Incorrect Answers
Separate identifiers may create separate charges.
An acknowledgment can be lost after commit.
Queue deduplication does not guarantee exactly-once financial side effects across provider timeouts or extended retries. The payment transaction needs a stable idempotency identity.






AWS Certified Solutions Architect - Associate SAA-C03 Practice Tests