You have semi-synchronous replication configured and working with one slave. rpl_semi_sync_master_timeout has never been reached.
You find that the disk system on the master has failed and as a result, the data on the master is completely unrecoverable.
Which two statements are true? (Choose two.)
With semi-synchronous replication, once a transaction is committed on the master, it waits until at least one slave acknowledges receipt of the transaction before confirming the commit. Thus, no committed transactions are lost, making it certain that the slave has the most up-to-date data available. However, since the slave applies transactions from its relay log, there might be a slight delay before all transactions are fully applied, leading to the possibility of reading outdated data immediately after the master fails.
A - With semi-synchronous replication, once the source commits a transaction, it waits until at least one replica has received and logged the events before confirming the commit. Therefore, if the source crashes, all committed transactions have been transmitted to at least one replica. E - The slave applies transactions from its relay log, and until it catches up with all transactions, there might be a delay in reading the most up-to-date data from the slave. https://dev.mysql.com/doc/refman/8.0/en/replication-semisync.html
Not E, a semi-sych means the slave has comitted the data before the Master returns ok to the app. There is nothing to catch up.
AC. D is loss of data
D is loss of data because rpi_semi_sync_master_timeout has nothing to do with relay logs.
No transaction shall lost in Semisynchronous Replication
Not D, rpl_semi_sync_master_timeout is a timeout when semi turns to asynchronous