In which two scenarios is an RMAN recovery catalog automatically resynchronized? (Choose two.)

Opening a database with the RESETLOGS option creates a new database incarnation, and RMAN automatically resynchronizes the recovery catalog to record the new incarnation information along with updated structural and backup metadata.

Archiving a redo log does not trigger an automatic recovery catalog resynchronization; archived log metadata is recorded in the catalog during subsequent backup operations or an explicit RESYNC CATALOG command.

When RMAN ages out backup metadata records from the control file based on the CONTROL_FILE_RECORD_KEEP_TIME parameter, an automatic resynchronization triggers so that the recovery catalog preserves records before they are purged from the control file.

Changing the backup retention policy configuration does not automatically resynchronize the catalog; a manual RESYNC CATALOG command is required to propagate such configuration changes.

A manual redo log switch does not trigger automatic recovery catalog resynchronization; log switches are local, control-file-level events that do not directly cause catalog updates.