Your question is Handle Idempotency in APIs. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
How do you handle idempotency in API requests?
Discuss how you would design idempotency for an API that may be retried because of timeouts, connection failures, or client uncertainty about whether a request succeeded. Cover request keys, durable state, concurrent duplicates, response replay, expiration, and behavior when the underlying operation partially fails.
