A, C. A Flashback Database recovery is best suited for a user error such as a truncated table or a logical corruption like an incomplete batch transaction affecting many tables. Media recovery situations cannot be performed with the Flashback Database recovery method.

D. A Flashback Database recovery can recover a large truncated table or group of tables.

B. The RVWR process is responsible for writing the "before" image information to the Flashback Database log. The Flashback Database log is read to perform the Flashback Database recovery.

D. The flash recovery area is a centralized storage area for backups on disk. This allows for a more efficient recovery process because the required files are in one location and are stored on disk instead of tape.

A, D. The Alert log reports space usage and other information about the flash recovery area. DBA_OUTSTANDING_ALERTS also show the information state of the flash recovery area.

B, C. The flash recovery area can be determined by either setting the initialization parameter DB_RECOVERY_FILE_DEST_SIZE or using the ALTER SYSTEM command.

A, C. The flash recovery area supports both the BACKUP and BACKUP COPY commands, which perform backup sets and image copies.

C. The dynamic view V$RECOVERY_FILE_DEST displays the space utilization and the amount of files that make up the flash recovery area.

D. The DB_FLASHBACK_RETENTION_TARGET parameter determines how much data is available to recover.

C. DB_FLASHBACK_RETENTION_TARGET is a parameter that is measured in minutes. This value determines how many minutes the Flashback Database should write data before this data gets overwritten.

A, C, D. To enable the Flashback Database, the flash recovery area must be created. The database must be mounted but not opened to turn on the Flashback Database. The database must also be in ARCHIVELOG mode.

A, B. The earliest timestamp and smallest SCN will tell you how far back you can recover the database. These values can be queried by the V$FLASHBACK_DATABASE_LOG dynamic view.

B. The V$DATABASE dynamic view has a new column called FLASHBACK_ON, which contains a value of YES or NO.

B. The V$FLASHBACK_DATABASE_STAT dynamic view shows the daily growth and utilization of the Flashback Database log. You can match daily activities to the daily utilization of the Flashback Database log.

A. The default size of a redo log file created in the flash recovery area is 100MB.

D. The LOG_ARCHIVE_DEST_n is the only initialization parameter that will create or write archive logs to the flash recovery area. ARCHIVE_LOG_DEST, ARCHIVE_DUPLEX_DEST, and ARCHIVE_LOG_DEST_n are not valid initialization parameters.

C, D. Control files and redo logs area considered permanent files in the flash recovery area. These files are not made obsolete and deleted, even when backed up to tape.

A, B, D, E. The flash recovery area will not back up redo log files, control files, or flashback logs with the BACKUP RECOVERY AREA and BACKUP RECOVERY FILES commands. Permanent files are considered to be current online redo logs and control files.

D. The RVWR process is responsible for writing the "before" images to the Flashback Database log. This process is also responsible for applying these to the database during a recovery.

C. Resizing of a tablespace or datafiles to a smaller size cannot be undone with Flashback Database recovery.