A.It uses a single master key for a database.

B.It encrypts only data on the client.

C.It can encrypt data at the column level.

D.It replaces secure application roles.

E.It stores the current and all past master keys in the keystore.

F.Master encryption keys are managed by Oracle Database Vault.

A.All files in the current FRA that have been backed up already, are backed up.

B.All files in any previous FRA that have not yet been backed up, are backed up.

C.All files in any previous FRA that have been backed up already, are backed up.

D.All Oracle recovery files normally written to the FRA and which have not yet been backed up, are backed up.

E.All Oracle recovery files normally written to the FRA and which have been backed up already to in any previous FRA, are backed up.

F.All files in the current fast recovery area (FRA) that have not yet been backed up, are backed up.

G.All Oracle recovery files normally written to the FRA and which have been backed up already to the current FRA, are backed up.

A.It is enabled by performing an Oracle Database installation with database creation and then running the roohctl-enable script.

B.It contains an image that can be distributed across multiple servers.

C.It is enabled by performing a software-only Oracle Database installation and then running the roohctl-enable script.

D.It requires the Rapid Home Provisioning service.

E.Its configuration data and log files reside in subdirectories under the Oracle home.

A.Oracle attempts to convert common users to conventional users when moving schemas from a PDB to a non-CDB.

B.Moving data from a PDB to a non-CDB is only possible by using transportable tablespace export and import.

C.Oracle attempts to convert conventional database users to local users when moving schemas from a non-CDB to a PDB.

D.A new PDB is automatically created when importing a non-CDB into a CDB.

E.Tablespaces are automatically created as need while importing full exports in either a non-CDB or a PDB.

F.Moving data from a non-CDB to a PDB is only possible by using conventional export and import.

A.A PDB snapshot can be a sparse copy of a source PDB.

B.A snapshot copy PDB can be a full copy of a source PDB.

C.A CDB can be duplicated using Recovery Manager (RMAN) with no configuration required before starting the duplication.

D.A snapshot copy PDB does not depend on an existing storage snapshot of the source PDB.

E.A PDB snapshot depends on an existing storage snapshot of the source PDB.

F.A CDB can be duplicated using the Database Configuration Assistant (DBCA) in silent mode with no configuration required before starting the duplication.

G.A PDB snapshot can be a full copy of a source PDB.