A.A Virtual Private Catalog used to register a container database must be created in a pluggable database.

B.A Virtual Private Catalog used to register a container database can be created in a pluggable database.

C.It Is always possible for RMAN to connect to a pluggable database as a target if any RMAN Catalog is used.

D.It is only possible for RMAN to connect to a pluggable database as a target if an RMAN Virtual Private Catalog is used.

E.It Is always possible for RMAN to connect to a pluggable database as a target.

F.A Virtual Private Catalog used to register a container database can be created in a non-container database.

A.A non-duplexed backup set written to SBT can be duplexed to disk by backing up the backup set that is already on tape.

B.A non-duplexed backup set written to disk can be duplexed to tape by backing up the backup set that is already on disk.

C.A duplexed backup set always uses twice as many SBT channels as a non-duplexed backup set for the same number of files.

D.A non-duplexed backup set written to SBT can be duplexed to tape by backing up the backup set that is already on tape.

E.A non-duplexed backup set written to disk can be duplexed to disk by backing up the backup set that is already on disk.

F.A duplexed backup set uses the same number of SBT channels as a non-duplexed backup set for the same number of files.

A.performing checks to ensure minimum configuration requirements for Oracle Grid Infrastructure are met

B.creating the oracle OS user

C.creating the OSDBA (dba) group

D.creating thte oraInventory (oinstall) group

E.creating the grid OS user

F.configuring the OS for Oracle Automatic Storage Management shared storage access

A.By default, AWR snapshots are retained for 7 days.

B.Its collection level is determined by the value of the STATISTICS_LEVEL database parameter.

C.AWR data is stored in the SYSTEM tablespace.

D.The taking of AWR snapshots can be disabled.

E.By default, AWR snapshots are taken every 60 minutes.

A.Fine-grained auditing (FGA) policies in an application root are automatically synchronized to all application PDBs contained in the application container.

B.Application-common OLS policies can be created in an application root inside an install/patch BEGIN-END block.

C.Application-common Oracle Label Security (OLS) policies cannot be created in an application root outside an install/patch BEGIN-END block.

D.Application-common TSDP policies are always container specific.

E.Application-common Transparent Security Data Protection (TSDP) policies can be created only within an application install/patch BEGIN-END block.

F.Unified auditing can be automatically synchronized to all application PDBs in an application container.

G.Virtual Private Database (VPD) policies on objects in an application root are automatically synchronized with all application PDBs contained in the application container.