recoverable and cascadeless

Question

Answer 1

Answer would be D

1- It is recoverable for sure.. Because nowhere any transaction has made write read conflict to be checked.  Property says you are not allowed to commit before transaction t which has made the modifications on same data which you have read after modification.

2- it is cascade less because property says you are not  allowed to read on same data  which is modified by  transaction t until t commits..  Here also no write read conflicts has been made therefore it is cascade less.

Answer 2

In these non serial schedule, there is no Dirty Read (Write -Read Conflict) so it is recoverable and Cascade less Schedule.