(Solved): Consider a DBMS using write-ahead logging with the STEAL and NO-FORCE buffer pool management policy. ...

Consider a DBMS using write-ahead logging with the STEAL and NO-FORCE buffer pool management policy. The log contains update records, checkpoints, and transaction begin/commit/abort records. Assume the DBMS executes a non-fuzzy checkpoint, where all dirty pages are written to disk. Its update record has the following form: Assume the DBMS uses the ARIES recovery protocol. The database has three transactions (T1, T2, T3) on three data objects (A, B, C). The following image has a table shows the log records available on disk after a crash: Q4)What should be the correct action on T1 when recovering the database from WAL? Question 4 options: redo all of T1's changes undo all of T1's changes do nothing to T1 Q5) What should be the correct action on T2 when recovering the database from WAL? Question 5 options: redo all of T2's changes undo all of T2's changes do nothing to T2 Q6) What should be the correct action on T3 when recovering the database from WAL? Question 6 options: redo all of T3's changes undo all of T3's changes do nothing to T3 Q7) Assume that the DBMS flushes all dirty pages when the recovery process finishes. What are the values of A, B, and C after the DBMS recovers the state of the database? Question 7 options: A=33, B=6, C=42 A=13, B=66, C=67 A=13, B=6, C=100 A=13, B=7, C=67 A=71, B=20, C=42 A=33, B=42, C=100 A=71, B=7, C=100 A=13, B=42, C=67 A=33, B=20, C=43 A=71, B=66, C=32 A=13, B=42, C=42 Not sure please provide the complete answer