Each question below shows the correct answer with a full explanation. Use these to build conceptual understanding before attempting a timed quiz.
Recovery ManagementEasy
Q1. Database recovery is the process of:
- A.Deleting all data from the tables in the entire database
- B.Restoring the database to a correct state after a failure✓ Correct
- C.Creating new tables and defining their column structures
- D.Optimizing queries by choosing better execution plans
Explanation
Recovery restores the database to a consistent state after a failure.
Report an error in this question
Recovery ManagementEasy
Q2. A transaction log (write-ahead log) records:
- A.Table structures and their column definitions in the database schema
- B.Only SELECT queries that have been executed against the database tables
- C.User login information and authentication credentials stored securely
- D.All changes made by transactions before they are applied to the database✓ Correct
Explanation
The transaction log records all modifications (before and after values) for recovery purposes.
Report an error in this question
Recovery ManagementEasy
Q3. The redo operation:
- A.Creates a new database from scratch without using any data from the previous state
- B.Re-applies changes of committed transactions that may not have been written to disk✓ Correct
- C.Undoes all changes of committed transactions and reverts to the original data state
- D.Deletes the entire log file and removes all records of previous transaction actions
Explanation
Redo reapplies committed transaction changes that may not have reached the disk before failure.
Report an error in this question
Recovery ManagementEasy
Q4. The undo operation:
- A.Reverses changes made by uncommitted transactions✓ Correct
- B.Creates a backup of the current database on disk
- C.Optimizes queries for faster execution performance
- D.Applies committed changes to the database on disk
Explanation
Undo reverses changes made by transactions that did not commit before the failure.
Report an error in this question
Recovery ManagementEasy
Q5. A checkpoint in database recovery is:
- A.A type of lock used to prevent concurrent access to shared data items
- B.An SQL statement used to query data from one or more database tables
- C.A point at which all modified data is written to disk and recorded in the log✓ Correct
- D.A type of index structure built on columns for faster data retrieval
Explanation
A checkpoint forces all modified buffers to disk and records a checkpoint entry in the log.
Report an error in this question
Recovery ManagementEasy
Q6. The Write-Ahead Log (WAL) protocol requires:
- A.Logs are only written to disk after the transaction has committed fully
- B.No log is needed for any database operations under this recovery protocol
- C.Data must be written to disk before the corresponding log records are made
- D.Log records must be written to disk before the corresponding data changes✓ Correct
Explanation
WAL requires that log records are written to stable storage before the actual database changes.
Report an error in this question
Recovery ManagementEasy
Q7. A system crash typically causes:
- A.Loss of data in main memory but not on disk✓ Correct
- B.No data loss of any kind after the crash
- C.Loss of all data everywhere in the system
- D.Loss of data on disk but not in main memory
Explanation
A system crash loses volatile (main memory) data while disk data typically survives.
Report an error in this question
Recovery ManagementEasy
Q8. A media failure refers to:
- A.Application crash caused by a software defect
- B.Network slowness affecting query response times
- C.Disk or storage device failure causing data loss✓ Correct
- D.Memory overflow due to excessive data loading
Explanation
Media failure involves damage to the storage medium (disk), causing loss of stored data.
Report an error in this question
Recovery ManagementEasy
Q9. Database backups are important for:
- A.Reducing table size by removing unnecessary data rows
- B.Recovering from media failures and catastrophic events✓ Correct
- C.Creating new databases from the backed up data copies
- D.Improving query speed and reducing execution latency
Explanation
Backups provide copies of the database for recovery from media failures and disasters.
Report an error in this question
Recovery ManagementEasy
Q10. An incremental backup stores:
- A.The entire database every single time
- B.Only the database schema definitions
- C.Only the changes since the last backup✓ Correct
- D.Only the transaction log file entries
Explanation
An incremental backup stores only the data that has changed since the last backup, saving time and space.
Report an error in this question
Recovery ManagementMedium
Q11. Deferred update (no-undo/redo) recovery technique:
- A.Requires neither undo nor redo operations during the recovery process
- B.Writes changes immediately and may need undo for uncommitted changes
- C.Does not write changes to disk until commit, so undo is never needed✓ Correct
- D.Does not use a log file for recording any of the transaction changes
Explanation
Deferred update postpones writing changes to disk until commit, eliminating the need for undo operations.
Report an error in this question
Recovery ManagementMedium
Q12. Immediate update recovery technique:
- A.Does not use a log file for any of the transaction record entries
- B.Writes changes only after commit, requiring only redo operations
- C.Requires only redo operations during the crash recovery process
- D.Writes changes to disk before commit, requiring both undo and redo✓ Correct
Explanation
Immediate update writes changes to disk before commit, so both undo (for uncommitted) and redo (for committed) may be needed.
Report an error in this question
Recovery ManagementMedium
Q13. Shadow paging recovery technique:
- A.Maintains two page tables: current and shadow✓ Correct
- B.Requires checkpoints at all times to function
- C.Uses only a log file for the recovery process
- D.Cannot handle any system crashes that may occur
Explanation
Shadow paging maintains a shadow copy of the page table; the shadow page table is the consistent backup.
Report an error in this question
Recovery ManagementMedium
Q14. After a crash, which transactions need to be redone?
- A.All transactions regardless of their commit state now
- B.Committed transactions whose changes may not be on disk✓ Correct
- C.Uncommitted transactions that were active during crash
- D.Only aborted transactions that failed before the crash
Explanation
Committed transactions are redone to ensure their changes are reflected in the database.
Report an error in this question
Recovery ManagementMedium
Q15. After a crash, which transactions need to be undone?
- A.All transactions regardless of their state at the time of the crash
- B.No transactions need to be undone during the recovery after a crash
- C.Transactions that were active (not committed) at the time of crash✓ Correct
- D.Committed transactions that completed successfully before the crash
Explanation
Active (uncommitted) transactions must be undone to remove their partial changes.
Report an error in this question
Recovery ManagementMedium
Q16. The ARIES recovery algorithm stands for:
- A.Automated Recovery and Integrity Enforcement System
- B.Advanced Recovery and Index Enhancement System
- C.Algorithm for Redo and Integrity Evaluation System
- D.Algorithm for Recovery and Isolation Exploiting Semantics✓ Correct
Explanation
ARIES stands for Algorithm for Recovery and Isolation Exploiting Semantics.
Report an error in this question
Recovery ManagementMedium
Q17. ARIES uses which three phases during recovery?
- A.Scan, Parse, Execute
- B.Analysis, Redo, Undo✓ Correct
- C.Lock, Execute, Unlock
- D.Read, Write, Commit
Explanation
ARIES recovery has three phases: Analysis (determine what needs to be done), Redo, and Undo.
Report an error in this question
Recovery ManagementMedium
Q18. A log sequence number (LSN) is:
- A.The total number of active transactions
- B.A type of lock used in concurrency control
- C.The size of the log file on stable storage
- D.A unique identifier for each log record✓ Correct
Explanation
An LSN uniquely identifies each log record and indicates its position in the log.
Report an error in this question
Recovery ManagementMedium
Q19. Fuzzy checkpointing differs from standard checkpointing in that:
- A.No log entry is written to record the occurrence of the checkpoint
- B.The database does not need to stop processing during the checkpoint✓ Correct
- C.All processing must stop completely during the checkpoint operation
- D.It occurs only once during the entire lifetime of the database
Explanation
Fuzzy checkpointing allows transactions to continue during the checkpoint process.
Report an error in this question
Recovery ManagementMedium
Q20. Physiological logging means:
- A.Log records describe changes at the page level with logical operations within the page✓ Correct
- B.Only logical operation names are logged without any reference to the physical pages
- C.Only physical byte-level changes are logged for each modification to the data pages
- D.No logging occurs at all for any modification made to the database during processing
Explanation
Physiological logging combines physical (page-level) and logical (operation-level) descriptions of changes.
Report an error in this question
Recovery ManagementHard
Q21. In ARIES, the analysis phase determines:
- A.The set of dirty pages and active transactions at crash time✓ Correct
- B.Only committed transactions that completed before the crash
- C.The hardware failure cause and the affected disk components
- D.Only the last checkpoint that was recorded in the log file
Explanation
The analysis phase scans the log from the last checkpoint to determine dirty pages and active transactions.
Report an error in this question
Recovery ManagementHard
Q22. In ARIES, the redo phase:
- A.Replays all logged changes from the earliest dirty page LSN forward✓ Correct
- B.Starts from the end of the log and processes records in reverse
- C.Only replays committed transactions and ignores uncommitted ones
- D.Undoes all transactions that were active at the time of the crash
Explanation
Redo in ARIES starts from the earliest LSN of dirty pages and replays all changes to restore the state at crash time.
Report an error in this question
Recovery ManagementHard
Q23. In ARIES, Compensation Log Records (CLRs) are:
- A.Checkpoint records that mark points of database consistency
- B.Log records for committed transactions only in the system
- C.Log records written during undo to record the undo actions✓ Correct
- D.Index maintenance records for B-tree structure updates
Explanation
CLRs are written during the undo phase to record undo actions, preventing re-undoing during repeated crashes.
Report an error in this question
Recovery ManagementHard
Q24. The steal/no-force buffer management policy means:
- A.Uncommitted pages can be written to disk (steal); committed need not be forced immediately (no-force)✓ Correct
- B.Committed pages are always forced to disk immediately; uncommitted pages are never written to disk
- C.Only committed pages are present on disk; uncommitted data remains exclusively in the memory buffer
- D.All pages are always kept in memory; nothing is written to disk until the entire database shuts down
Explanation
Steal allows writing uncommitted data to disk; no-force doesn't require committed data to be immediately written to disk.
Report an error in this question
Recovery ManagementHard
Q25. No-steal/force policy would mean:
- A.Uncommitted pages are never written to disk, and committed pages are always forced to disk✓ Correct
- B.Neither undo nor redo is needed with this policy since both cases are eliminated
- C.Uncommitted pages can be written to disk at any time before the transaction commits
- D.Committed pages may not be on disk immediately and can remain only in memory buffer
Explanation
No-steal/force eliminates the need for undo (no uncommitted data on disk) and redo (committed data always on disk).
Report an error in this question
Recovery ManagementHard
Q26. The redoLSN in ARIES is:
- A.The checkpoint LSN that marks the most recent consistency checkpoint
- B.The last LSN that was recorded in the transaction log before the crash
- C.The LSN from which redo must start (earliest recLSN among dirty pages)✓ Correct
- D.The LSN of the last commit record written to the stable storage log
Explanation
The redoLSN is the earliest recLSN in the dirty page table, indicating where redo must begin.
Report an error in this question
Recovery ManagementHard
Q27. Write-ahead logging requires that log records be written to stable storage before:
- A.The transaction starts its initial read operation
- B.Any query is executed against the database tables
- C.The corresponding data page is flushed to disk✓ Correct
- D.The user submits the query to the database system
Explanation
WAL requires log records to reach stable storage before the modified data pages are written to disk.
Report an error in this question
Recovery ManagementHard
Q28. In ARIES, when a transaction is undone, the undo follows:
- A.The commit order of other transactions in the same schedule
- B.The table creation order defined in the database schema file
- C.The lastLSN chain backward through that transaction's log records✓ Correct
- D.A random order without any specific sequence or priority rules
Explanation
Undo follows the chain of prevLSN pointers backward through the transaction's own log records.
Report an error in this question
Recovery ManagementHard
Q29. Remote backup systems for disaster recovery provide:
- A.A copy of the database at a geographically separate site✓ Correct
- B.Better index structures for improving search performance
- C.Improved normalization of tables to reduce data redundancy
- D.Faster query processing through parallel execution plans
Explanation
Remote backup systems maintain a database copy at a distant location for disaster recovery.
Report an error in this question
Recovery ManagementHard
Q30. The concept of idempotent redo means:
- A.Applying redo multiple times produces the same result as applying it once✓ Correct
- B.Redo can only be applied once and cannot be repeated after that point
- C.Redo changes the result each time it is applied to the database state
- D.Redo is never repeated because recovery always succeeds on first try
Explanation
Idempotent redo ensures that re-applying the redo operation produces the same state, important for crash during recovery.
Report an error in this question