Transactions coordinate multiple document changes but add operational cost and failure handling. They do not remove the need for a sensible model.
Before you start
You should understand documents, collections and indexes. Sketch representative documents and the reads and writes they must support. MongoDB-specific examples assume a collection with the shown fields; deployment topology, permissions and existing indexes can affect the operational behavior being discussed.
The practical goal is to reason through this situation: A transfer affecting separate account records may require a transaction. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.
Step-by-step walkthrough
Step 1: Identify cross-document invariants
Two account balances may require coordinated changes.
Step 2: Consider natural embedding
Bounded data belonging together can use document atomicity instead.
Step 3: Keep transaction work focused
Avoid slow remote calls and handle transient or uncertain outcomes appropriately.
Worked scenario
A transfer affecting separate account records may require a transaction.
A transfer decreases one account and increases another. Without coordination, a failure between updates loses or creates apparent value. A transaction can protect that local invariant, but it does not atomically include a remote payment provider; external effects still require separate workflow ownership.
Common mistake
Long transactions and remote calls increase contention and uncertainty.
Verify the behavior
Fail between updates and verify neither partial transfer persists.
Interview exercise
Decide whether to embed first.
Answer and reasoning
Keep naturally bounded atomic data together, then use transactions for invariants genuinely spanning separate documents.
Continue learning
Compare the scenario with the MongoDB interview questions and test your understanding with the MongoDB MCQs. For terminology and implementation details, consult the reference material.