In DBMS when a transaction completes its execution it is said to be:

Question

Accepted Answer

The correct option is (4):
When a transaction successfully completes all its operations and the changes are finalized, it is technically said to be **Committed**. This is the final and crucial stage of a transaction life cycle, often corresponding to the execution of the `COMMIT` command in SQL. Commitment guarantees that the changes made by the transaction are permanent and durable, meaning they will not be lost even if the system subsequently crashes or loses power. This feature directly supports the **Durability** property, one of the four foundational ACID (Atomicity, Consistency, Isolation, Durability) properties that ensure the reliability and integrity of database transactions. Once committed, the transaction’s results are permanently incorporated into the database and made visible to all other transactions.

The incorrect option is (1):
The term **Saved** is a general computing term used to describe writing data to permanent storage, but it is not the precise technical term used in Database Management Systems (DBMS) to describe the state of a successfully executed transaction. While a committed transaction is indeed saved, the technical language of transaction management reserves the word **Committed** to signify that the database has guaranteed the changes satisfy the ACID properties, especially durability and consistency.

The incorrect option is (2):
**Loaded** refers to the act of bringing data, a program, or a process from secondary storage (like a hard disk) into the main memory (RAM) for execution. This is an operation related to memory management and process initiation, not the final termination state of a database transaction. A transaction is a logical unit of work, and while its operations involve loading data, the final result of its execution is either committed or aborted.

The incorrect option is (3):
**Rolled** is an informal reference to the action of **Rolling Back** (or aborting) a transaction. A transaction is rolled back when it **fails** to complete all its operations, encounters an error, or is explicitly aborted. The rollback process undoes all partial changes made by the transaction, ensuring that the database returns to its last consistent state, thereby adhering to the **Atomicity** property of ACID. Therefore, it is the state for an unsuccessful transaction, the opposite of a successfully completed one.