Your database is configured for ARCHIVELOG mode, and a daily full database backupis taken. RMAN is configured to perform control file autobackup. In which three scenarios do you need media recovery?

The loss of all control file copies is a critical failure requiring media recovery, typically involving restoring a control file autobackup, then restoring data files, and applying archived redo logs.

If all members of an inactive online redo log group are lost and their contents are required to apply changes to restored data files (e.g., if the corresponding archived redo logs are also unavailable or lost), then media recovery is necessary to prevent data loss or achieve point-in-time recovery.

Loss of a data file belonging to the active undo tablespace renders the database inconsistent and necessitates media recovery to restore the undo segments and bring the database to a consistent state.

Loss of SYSTEM tablespace data files is a catastrophic event that absolutely requires media recovery (restoring the SYSTEM data files and applying redo logs) to make the database functional again.

Logical corruption often requires point-in-time recovery (a form of media recovery) or using flashback database, but the question may be implicitly focused on physical data loss requiring direct restore-and-recover operations.

An abnormal termination of the database instance triggers automatic instance recovery upon startup, which processes redo logs to roll forward committed transactions and roll back uncommitted ones, and does not require manual media recovery.