Each question below shows the correct answer with a full explanation. Use these to build conceptual understanding before attempting a timed quiz.
Transaction ManagementEasy
Q1. ACID properties of a transaction stand for:
- A.Atomicity, Concurrency, Isolation, Durability
- B.Addition, Consistency, Integrity, Durability
- C.Atomicity, Consistency, Isolation, Durability✓ Correct
- D.Atomicity, Consistency, Isolation, Dependency
Explanation
ACID stands for Atomicity, Consistency, Isolation, and Durability.
Report an error in this question
Transaction ManagementEasy
Q2. Atomicity means that a transaction:
- A.Runs in isolation from all other transactions
- B.Is either fully completed or fully rolled back✓ Correct
- C.Is stored permanently on the disk after start
- D.Can be partially completed and then paused
Explanation
Atomicity ensures a transaction is treated as a single indivisible unit — all or nothing.
Report an error in this question
Transaction ManagementEasy
Q3. Consistency ensures that a transaction:
- A.Never fails regardless of the operations within
- B.Is stored permanently on disk after the commit
- C.Runs concurrently with other active transactions
- D.Brings the database from one valid state to another✓ Correct
Explanation
Consistency ensures the database remains in a valid state before and after a transaction.
Report an error in this question
Transaction ManagementEasy
Q4. Isolation ensures that:
- A.Transactions are never allowed to execute concurrently
- B.All transactions see each other's changes immediately
- C.Only one transaction can exist in the system at a time
- D.Concurrent transactions do not interfere with each other✓ Correct
Explanation
Isolation ensures that concurrent transactions execute as if they were running serially.
Report an error in this question
Transaction ManagementEasy
Q5. Durability ensures that:
- A.Data is stored only in volatile memory and not on stable disk
- B.Changes can be undone at any time even after transaction commit
- C.Committed transaction changes persist even after system failure✓ Correct
- D.Transactions are temporary and their changes are never saved
Explanation
Durability guarantees that once a transaction is committed, its changes are permanent.
Report an error in this question
Transaction ManagementEasy
Q6. The COMMIT operation in a transaction:
- A.Pauses the active transaction
- B.Makes all changes permanent✓ Correct
- C.Undoes all current changes
- D.Starts a new transaction
Explanation
COMMIT makes all changes made by the transaction permanent in the database.
Report an error in this question
Transaction ManagementEasy
Q7. The ROLLBACK operation in a transaction:
- A.Undoes all changes made by the transaction✓ Correct
- B.Starts a new transaction in the session
- C.Deletes the database and all stored data
- D.Saves all changes and makes them permanent
Explanation
ROLLBACK undoes all changes made during the current transaction.
Report an error in this question
Transaction ManagementEasy
Q8. A transaction that has not yet been committed or rolled back is called:
- A.Committed
- B.Active✓ Correct
- C.Aborted
- D.Terminated
Explanation
An active transaction is one that is currently executing and has not yet committed or aborted.
Report an error in this question
Transaction ManagementEasy
Q9. Which of the following is a transaction state?
- A.All of these: Active, Partially committed, Committed, Failed, Aborted✓ Correct
- B.Only Aborted is considered a valid state for a transaction process
- C.Only Active is considered a valid state for a transaction in a DBMS
- D.Only Committed is considered a valid state for a transaction to be
Explanation
Transaction states include Active, Partially committed, Committed, Failed, and Aborted.
Report an error in this question
Transaction ManagementEasy
Q10. A schedule in transaction management is:
- A.A single SQL query executed against the database tables
- B.A backup plan for recovering from a system level failure
- C.A type of index structure for speeding up data lookups
- D.A sequence of operations from one or more transactions✓ Correct
Explanation
A schedule is a chronological ordering of operations from concurrent transactions.
Report an error in this question
Transaction ManagementMedium
Q11. A serial schedule is one where:
- A.Only one transaction is allowed in the database system total
- B.Operations are randomly ordered across multiple transactions
- C.Transactions execute one after another without interleaving✓ Correct
- D.Transactions execute concurrently with operations interleaved
Explanation
A serial schedule executes transactions sequentially with no interleaving of operations.
Report an error in this question
Transaction ManagementMedium
Q12. A serializable schedule is:
- A.A schedule whose result is equivalent to some serial schedule✓ Correct
- B.A schedule where all transactions run simultaneously at once
- C.A schedule that is always a serial schedule by definition
- D.A schedule with no transactions present within its timeline
Explanation
A serializable schedule produces the same result as some serial execution of the same transactions.
Report an error in this question
Transaction ManagementMedium
Q13. Conflict serializability is tested using:
- A.Hash table (bucket-based structure)
- B.B-tree index (balanced tree structure)
- C.ER diagram (entity relationship model)
- D.Precedence graph (serialization graph)✓ Correct
Explanation
A precedence graph determines conflict serializability — if it has no cycles, the schedule is conflict serializable.
Report an error in this question
Transaction ManagementMedium
Q14. Two operations conflict if:
- A.They belong to different transactions, access the same data item, and at least one is a write✓ Correct
- B.They are both read operations accessing the same data item from within different transactions
- C.They belong to the same transaction and access different data items within the transaction
- D.They access different data items from different transactions without any write operations
Explanation
Conflicting operations are from different transactions, access the same item, and at least one writes.
Report an error in this question
Transaction ManagementMedium
Q15. A dirty read occurs when:
- A.No read operation occurs between any concurrent transactions
- B.A transaction reads data that it has written by itself before
- C.A transaction reads data written by an uncommitted transaction✓ Correct
- D.A transaction reads data that has already been fully committed
Explanation
A dirty read occurs when a transaction reads data that has been modified by another transaction that has not yet committed.
Report an error in this question
Transaction ManagementMedium
Q16. A non-repeatable read occurs when:
- A.No read operation is performed during the entire transaction
- B.All reads from a transaction return the same consistent value
- C.A transaction reads a value once and never accesses it again
- D.A transaction reads the same item twice and gets different values✓ Correct
Explanation
Non-repeatable read occurs when a transaction reads the same data item twice and finds it changed by another committed transaction.
Report an error in this question
Transaction ManagementMedium
Q17. A phantom read occurs when:
- A.A transaction re-executes a query and finds new rows added by another transaction✓ Correct
- B.A transaction reads no rows at all from the table during its entire execution
- C.A transaction creates a table and populates it with data from another data source
- D.A transaction deletes rows from the table and those changes are then committed
Explanation
Phantom reads occur when a transaction re-reads and finds new rows that were inserted by another committed transaction.
Report an error in this question
Transaction ManagementMedium
Q18. The READ UNCOMMITTED isolation level allows:
- A.No anomalies of any kind during transaction processing
- B.Dirty reads, non-repeatable reads, and phantom reads✓ Correct
- C.Only phantom reads but prevents all other read anomalies
- D.Only non-repeatable reads but prevents all dirty reads
Explanation
READ UNCOMMITTED is the lowest isolation level, allowing dirty reads, non-repeatable reads, and phantom reads.
Report an error in this question
Transaction ManagementMedium
Q19. The SERIALIZABLE isolation level provides:
- A.Complete isolation from other transactions✓ Correct
- B.Only dirty read prevention mechanism
- C.Faster performance than other levels
- D.No isolation between any transactions
Explanation
SERIALIZABLE provides the highest isolation level, preventing all concurrency anomalies.
Report an error in this question
Transaction ManagementMedium
Q20. A cascading rollback occurs when:
- A.No rollback is needed because every transaction completes without any failures
- B.Only one transaction rolls back while all other transactions continue normally
- C.One transaction's rollback forces other dependent transactions to also roll back✓ Correct
- D.All transactions commit successfully without any errors during their execution
Explanation
Cascading rollback happens when an aborted transaction causes other transactions that read its uncommitted data to also roll back.
Report an error in this question
Transaction ManagementHard
Q21. View serializability is:
- A.Not related to serializability in any way
- B.Less restrictive than conflict serializability✓ Correct
- C.The same as conflict serializability criteria
- D.More restrictive than conflict serializability
Explanation
View serializability is less restrictive (allows more schedules) than conflict serializability.
Report an error in this question
Transaction ManagementHard
Q22. A recoverable schedule ensures that:
- A.A transaction commits only after all transactions whose data it read have committed✓ Correct
- B.All transactions must run serially with no concurrent execution allowed at all
- C.Transactions can commit in any order regardless of their data reading dependencies
- D.Rollbacks are never needed because all transactions always complete successfully
Explanation
In a recoverable schedule, if transaction Tj reads data written by Ti, then Ti must commit before Tj.
Report an error in this question
Transaction ManagementHard
Q23. A cascadeless schedule is one where:
- A.All transactions must abort immediately
- B.Transactions only read committed data✓ Correct
- C.Transactions can read uncommitted data
- D.No reads are allowed in any transaction
Explanation
A cascadeless schedule avoids cascading rollbacks by ensuring transactions only read committed data.
Report an error in this question
Transaction ManagementHard
Q24. A strict schedule requires that:
- A.No transaction reads or writes data written by an uncommitted transaction✓ Correct
- B.Transactions can freely read uncommitted data from other transactions
- C.Commits are not required for transactions to be considered complete
- D.Only serial schedules are allowed for all transactions in the system
Explanation
A strict schedule prevents both reading and writing of data items written by uncommitted transactions.
Report an error in this question
Transaction ManagementHard
Q25. The precedence graph for testing conflict serializability has:
- A.Nodes for SQL statements and edges for their execution ordering
- B.Nodes for transactions and edges for conflicting operation pairs✓ Correct
- C.Nodes for data items and edges for transactions accessing them
- D.No nodes or edges are used in this graph representation at all
Explanation
The precedence graph has transactions as nodes and directed edges based on conflicting operations order.
Report an error in this question
Transaction ManagementHard
Q26. Testing view serializability is:
- A.NP-complete✓ Correct
- B.Linear time
- C.Logarithmic time
- D.Constant time
Explanation
Testing whether a schedule is view serializable is NP-complete, unlike conflict serializability which is polynomial.
Report an error in this question
Transaction ManagementHard
Q27. The READ COMMITTED isolation level prevents:
- A.No anomalies of any kind
- B.All anomalies including phantoms
- C.Only dirty reads alone✓ Correct
- D.Dirty and non-repeatable reads
Explanation
READ COMMITTED prevents dirty reads but still allows non-repeatable reads and phantom reads.
Report an error in this question
Transaction ManagementHard
Q28. The REPEATABLE READ isolation level prevents:
- A.All anomalies including phantom reads
- B.Dirty reads and non-repeatable reads✓ Correct
- C.Only dirty reads from transactions
- D.No anomalies of any kind at all
Explanation
REPEATABLE READ prevents dirty reads and non-repeatable reads but may still allow phantom reads.
Report an error in this question
Transaction ManagementHard
Q29. In a multi-version concurrency control (MVCC) system:
- A.Transactions must be serial with no concurrent execution allowed at all
- B.Multiple versions of data items are maintained for concurrent access✓ Correct
- C.Only one version of each data item exists at any given point in time
- D.Locks are always required for every read and write operation performed
Explanation
MVCC maintains multiple versions of data items so readers don't block writers and vice versa.
Report an error in this question
Transaction ManagementHard
Q30. A blind write is:
- A.A committed transaction that has been successfully applied
- B.A query optimization technique that reduces disk access
- C.A read operation that is not followed by any write at all
- D.A write operation without reading the current value first✓ Correct
Explanation
A blind write occurs when a transaction writes a data item without reading its current value first.
Report an error in this question