A.RMAN always uses an auxiliary instance.

B.RMAN can recover tables in the SYSAUX tablespace.

C.RMAN can recover a table after a DDL operation has altered the table structure.

D.RMAN can recover tables owned by the SYS user.

E.RMAN can recover tables owned by the SYSTEM user.

F.RMAN can recover tables in a standby database.

G.RMAN can recover tables in the SYSTEM tablespace.

A.A PDB snapshot is always a full copy of the source PDB.

B.A snapshot copy PDB depends on a storage snapshot which can be stored on any file system.

C.A PDB snapshot depends on a storage snapshot which can be stored on any file system.

D.A snapshot copy PDB can be created from a stand-alone clone PDB.

E.A snapshot copy PDB depends on a storage snapshot which can only be stored on specific file systems.

F.A PDB snapshot depends on a storage snapshot which can only be stored on specific file systems.

G.A PDB snapshot is always a sparse copy of the source PDB.

A.An application root PDB is created for APP1.

B.A default service Is created for the application root APP1.

C.An application seed PDB Is created for APP1.

D.APP1 can never be unplugged.

E.Application PDBs that are subsequently created in the APP1 application container will be cloned from PDB$SEED.

F.Application PDBs that are subsequently created in the APP1 application container will be cloned from APP1$SEED.

A.after losing a SYSAUX tablespace data file

B.after losing all members of an INACTIVE online redo log group

C.after losing all members of the CURRENT online redo log group

D.after losing all copies of the control file

E.after losing an UNDO tablespace that is in use

A.Only consistent backups can be created.

B.The database must be registered in an RMAN catalog.

C.Backups must be done incrementally.

D.Backups can be done incrementally.

E.Backups must be contained in backup sets.

F.Backups can be taken only if the database is in archivelog mode.