3995. API idempotency: Insert a payment request only once by a unique idempotency key. — Architecture

DBMS Published 30 Sept 2026 Updated 30 Sept 2026 0 Views Verified

In a api idempotency module, solve this as a production problem using Architecture: Insert a payment request only once by a unique idempotency key. Provide the SQL, explain the logic, show safe application integration, and mention failure/edge cases.

Looking for the latest Sarkari Result 2026 updates? Check the latest government exam results, merit lists and result updates on Sarkari Resultess.

Answer & Explanation

4 Answers

Verified

Option A

DELETE FROM table_name;

Additional Explanation

Incorrect: it does not satisfy the stated business rule and can return/change unintended data.

Verified

Option B

SELECT * FROM table_name;

Additional Explanation

Incorrect: it does not satisfy the stated business rule and can return/change unintended data.

Verified

Option C

UPDATE table_name SET status='active';

Additional Explanation

Incorrect: it does not satisfy the stated business rule and can return/change unintended data.

Verified Correct Answer

Option D

INSERT INTO payments(idempotency_key,order_id,amount,status) VALUES(:key,:order_id,:amount,'pending') ON DUPLICATE KEY UPDATE id=id;

Additional Explanation

The unique key makes retries safe; the no-op update returns the existing row path without creating a duplicate.