Context: Database transactions can be used to introduce some level of fault tolerance and data integrity after recovery from a crash. A database transaction is a unit of work, typically encapsulating a number of operations over a database (e.g., reading a database object, writing, acquiring lock, etc.), an abstraction supported in database and also other systems. Each transaction has well defined boundaries in terms of which program/code executions are included in that transaction (determined by the transaction's programmer via special transaction commands).

Question: What is a unit of work called in a database?
Answer: transaction

Question: How can database transactions ensure accuracy after a crash?
Answer: fault tolerance

Question: Are transactions limited?
Answer: Each transaction has well defined boundaries

Question: What is a unit of play called in a database?
Answer: Unanswerable

Question: How can database transactions lower accuracy after a crash?
Answer: Unanswerable

Question: What has poorly defined boundaries in a database?
Answer: Unanswerable

Question: What has no ability to recover from a crash?
Answer: Unanswerable

Question: What always encapsulates only one transaction?
Answer: Unanswerable