C. All the Flashback Technologies, with the exception of the Flashback Database, utilize the undo data to recover objects.

B, D. The Recycle Bin is a logical container of flashback dropped objects. The objects in the Recycle Bin are stored in the tablespace they were created in.

D. The Flashback Drop process is responsible for backing up tables and their dependent objects.

E. Only non-partitioned index-organized tables are protected by the Recycle Bin. Non-system and locally managed tablespaces are stored in the Recycle Bin. Referential constraints are not stored in the Recycle Bin. DML or DDL cannot be performed against objects in the Recycle Bin.

A. The command DROP USER user CASCADE drops the user and the database objects without recording a backup in the Recycle Bin. Objects in the Recycle Bin owned by the user will be removed from the Recycle Bin.

C. The PURGE DBA_RECYCLEBIN command purges the complete Recycle Bin for all users.

A. The naming convention of objects in the Recycle Bin consists of a globalUID and version number assigned by the database with BIN$ prefixed, and a $ between the globalUID and the version number. The formatting looks like BIN$globalUID $version.

A, D. The SHOW RECYCLEBIN command and querying the RECYCLEBIN view are two methods of viewing the contents of the Recycle Bin.

C. The Recycle Bin is not stored in a Recycle Bin tablespace. It is a logical container pointing to objects in the tablespace where the objects were originally created. Objects are removed from the Recycle Bin when there is a need for available extents in a non-system tablespace. The objects are removed on a first in, first out (FIFO) basis.

B. A tablespace with AUTO EXTEND enabled will not autoextend to make space for the Recycle Bin objects. The objects will be removed from the Recycle Bin in the standard first in, first out (FIFO) basis.

B. Flashback Versions Query is a method of querying all version changes on rows. The rows must exist from the time the query was executed to a point-in-time in the past. The query will not display committed data after the query has been executed.

A. The view FLASHBACK_TRANSACTION_QUERY is used as a diagnostic tool to identify version information about transactional changes to the database. This view can be used to view the DML statements that were executed against a row and in a specific table.

A, C. The Flashback Versions Query can be performed by either MINVALUE and MAXVALUE SCN or starting and ending TO_TIMESTAMP value.

C. The VERSIONS BETWEEN clause of the Flashback Versions Query cannot query past table modifications or DDL changes to a table.

A. VERSIONS_XID uniquely identifies a row in the Flashback Versions Query. The other pseudocolumns can narrow down the selection criteria and may identify multiple rows in a timeframe or SCN range.

A, B. The VERSIONS BETWEEN clause can be used in DML and DDL statements to identify data.

B. The command ALTER TABLE table_name ENABLE ROW MOVEMENT must be enabled to allow Flashback Table recovery.

A, C. The default action for the FLASHBACK TABLE command is that the triggers will be disabled. If you disable the triggers on a table, the triggers will stay disabled after the FLASHBACK TABLE command as well. Also, if you use the ENABLE TRIGGER clause, all enabled triggers on the table prior to the Flashback Table operation will be enabled and all disabled triggers will be disabled.

B, C. The proper method is to query the FLASHBACK_TRANSACTION_QUERY view. The TABLE_NAME, OPERATION, and UNDO_SQL columns should be queried to display the information about the transactional information. The transactional information from FLASHBACK_TRANSACTION_QUERY should then be narrowed down by START_TIMESTAMP or START_SCN. Then the information can be further narrowed down by TABLE_OWNER. Alternatively, the XID, if known, can be queried to identify the exact transaction, but that was not an option in this example.

B. Adding RETENTION GUARANTEE to the UNDO tablespace or during database creation to the UNDO tablespace will protect unexpired undo data in the UNDO tablespace. This is where the Flashback Transaction Query retrieves information about transaction changes to rows in the database.