Final answer:
A DBMS indeed sees a transaction as a series of reads and writes ending with a commit or abort, which is true. Transactions are vital for maintaining data integrity and consistency and adhere to the ACID properties. The statement is A. true.
Step-by-step explanation:
The statement that a DBMS (Database Management System) sees a transaction as a series of reads, writes, and a commit/abort is true.
A transaction in database systems is a unit of work that is treated in a coherent and reliable way independent of other transactions.
The primary operations involved in a transaction are typically reads (retrieving data from the database), writes (updating data in the database), and finally either committing the transaction (which means the changes are permanently applied) or aborting it (which means the changes are rolled back and not applied).
Transactions are crucial for ensuring data integrity and consistency. They follow the ACID properties, which stand for Atomicity, Consistency, Isolation, and Durability, to ensure that the database remains accurate and reliable even in the event of system failures or concurrent access.