All quizzesHard
Consistency & Data Architecture — Series 3
Preview — 3 of 10 questions
A retried POST uses the same idempotency key but a different request body. What should the server's durable idempotency record help detect?
AA conflicting reuse of the key rather than silently returning an unrelated result
BA reason to create both resources
CAn automatic new key generated by OpenAPI
DA database migration request
A commit times out and the client retries. Why is blindly repeating the INSERT dangerous?
AA timeout guarantees rollback
BThe first transaction may have committed even though its response was lost
CSQLModel always deduplicates equal objects
DFastAPI changes POST to GET on retry
Two workers process the same outbox event after a lease expires. What property should downstream handling have?
AAn expectation that every event is delivered exactly once automatically
BA response model that hides duplicates
CIdempotent or deduplicated event application
DA separate database schema per worker
Sign up free to play
Answer all 10 questions (7 more), see explanations for every answer, and track your score.