A.A database can be flashed back using SQL*PLUS.

B.It always generates REDO and UNDO.

C.It requires that the target database be in ARCHIVELOG mode.

D.FLASHBACK LOGS are archived after a log switch.

E.Queries and DML have the same FLASHBACK LOG overhead when flashback is enabled for a database.

F.FLASHBACK DATABASE only uses FLASHBACK LOGS to get the database to the desired flashback time.

A.Backing up a database in noarchivelog mode using O/S utilities requires that the database instance be started and the database be in mount state.

B.Oracle archive log backups, copied using an O/S utility, can be added to the RMAN catalog as a backup set.

C.Backing up a database in archivelog mode using O/S utilities requires that the database instance be started and the database be in open state.

D.Backing up a database in archivelog mode using O/S utilities requires that the database instance be started and the database be in mount state.

E.Backing up a database in noarchivelog mode using O/S utilities requires that the database instance be shut down.

F.An Oracle database can be restored from backup files copied using O/S utilities.

G.Oracle data file backups, copied using an O/S utility, can be added to the RMAN catalog as image copies.

A.Flashback logs are automatically purged whenever the value of
DB_FLASHBACK_RETENTION_TARGET is changed.

B.Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET before there is space pressure.

C.Flashback logs are automatically purged when DB_FLASHBACK_RETENTION_TARGET is set lower than the time they have already been retained.

D.Flashback logs are monitored for being older than the retention period defined in DB_FLASHBACK_RETENTION_TARGET and can be deleted by an administrator written event trigger.

E.Flashback logs are monitored and proactively deleted when beyond the retention period defined in DB_FLASHBACK_RETENTION_TARGET only after there is space pressure.

A.The auxiliary instance is automatically created with ENABLE_PLUGGABLE_DATABASE = TRUE.

B.A user with SYSDBA or SYSBACKUP must be logged in with RMAN to the PDB to duplicate it.

C.CDB$ROOT and PDB$SEED are automatically duplicated.

D.All tablespaces belonging to a PDB must be duplicated when duplicating the PDB.

E.Two or more PDBs can be duplicated with the same RMAN DUPLICATE command.

A.to specify the list of user tablespaces to include when moving a non-CDB to a PDB

B.to include specific user tablespaces only when relocating a PDB

C.to exclude all tablespaces except SYSTEM, SYSAUX, and TEMP when plugging in a PDB

D.to exclude a temp tablespace when plugging in a PDB

E.to specify the list of tablespaces to include when creating a PDB from the CDB seed

F.to specify a default tablespace in a PDB cloned from another PDB in the same CDB.