codejump

Consistency & Data Architecture — Series 2

Preview — 3 of 10 questions

A POST idempotency key is recorded only in process memory. Why is that insufficient behind multiple FastAPI workers?

ARetries may hit a different worker and execute again
BFastAPI shares Python dictionaries across processes
CIt makes database writes atomic automatically
DThe key becomes an HTTP response model

A payment API scopes idempotency keys only by their text, even though different clients can choose the same key. What should the durable uniqueness rule include?

AOnly the current worker's process ID
BThe client or account scope as well as the key
CThe response model's class name
DOnly the request timestamp

A workflow commits a row and then calls an external service synchronously. The external call fails. What cannot an ordinary database rollback undo?

AA still-uncommitted flush
BA pending in-memory model change
CThe already committed row
DThe request's query parameters

Sign up free to play

Answer all 10 questions (7 more), see explanations for every answer, and track your score.