Which two are prerequisites for performing a flashback transaction?

Flashback Database enables point-in-time recovery of the entire database using flashback logs, but it is not a prerequisite for flashback transaction, which uses undo data instead.

Undo retention guarantee ensures undo data is not overwritten prematurely, but it is a best-practice consideration rather than a hard prerequisite for performing a flashback transaction.

The EXECUTE privilege on the DBMS_FLASHBACK package is required because flashback transaction operations are performed via this package's procedures, and without this privilege the user cannot invoke the necessary flashback functionality.

Supplemental logging must be enabled because flashback transaction relies on additional column data written to the redo log - specifically, supplemental logging records the before-images of changed columns needed to construct the compensating SQL that reverses a transaction.

The recycle bin is used by Flashback Drop to recover dropped tables, not by flashback transaction, which operates on undo segments to reverse DML changes.

Block change tracking records which database blocks changed to speed up incremental RMAN backups and has no relationship to flashback transaction functionality.