Idempotency in APIs — Concept Check
Questions on Idempotency in APIs. An idempotent operation produces the same result when called multiple times; implement via idempotency keys stored in Redis or a DB to deduplicate retries.
Questions in this quiz
7 questions on Idempotency in APIs — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A client retries a POST request to a payment service due to a network issue. What ensures the customer isn't charged twice?
- ASwitching to a GET request
- BImplementing exponential backoff for retries
- CUsing an idempotency key with each retry
- DIncreasing the timeout for the request
2.A service uses Redis to store idempotency keys. What happens if a key is not found in Redis during a request?
- AThe server waits for the key to appear
- BThe request proceeds normally as it's considered new
- CThe server throws an error
- DThe request is rejected immediately
3.In a distributed system, why might a POST request be repeated multiple times?
- ANetwork unreliability causing retries
- BThe client misconfigures the request
- CThe operation is inherently repeatable
- DThe server requests multiple attempts
4.A developer uses INSERT ... ON CONFLICT in Postgres for idempotency. What is the benefit?
- AReduces database storage requirements
- BImproves query execution speed
- CSimplifies query syntax
- DEnsures atomic check-and-insert operations
5.A client generates a UUID for each payment operation. Why is this important?
- AHelps in tracking the number of retries
- BEnsures each logical operation is uniquely identified
- CIncreases the randomness of the request
- DReduces the payload size of the request
6.Why might a Redis-based idempotency implementation use a 24-hour TTL for keys?
- ATo ensure keys are always available
- BTo comply with HTTP caching standards
- CTo limit memory usage by expiring old keys
- DTo match the client's retry interval
7.What is a key advantage of using Redis for idempotency key storage?
- AAutomatic key generation
- BBuilt-in support for JSON
- CFast access and TTL-based expiry
- DGuaranteed durability of data