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

It requires the Rapid Home Provisioning service.

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

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

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

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

Application-common TSDP policies are always container specific.

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

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

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

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

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

A target database’s persistent RMAN configuration settings are always stored in the target’s control file

Backup older than the recovery window retention policy are always deleted automatically if the backup location has insufficient space.

Backups written to the fast recovery area (FRA) that are oboslete based on the redundancy retention policy can be deleted automatically to free space.

The RMAN SHOW ALL command displays only settings with nondefault values.

A target database’s persistent RMAN configuration settings are always synchronized automatically with the RMAN catalog.

The V$RMAN_CONFIGURATION view displays only settings with valuesthat have been modified. G)A DBA must specify either a redundancy retention policy or a recovery window retention policy.

They are installed via OPatch or OPatchAuto.

A base release is not needed to install patchsets.

They can be applied in a rolling fashion for Clusterware and the databases.

Installing a patchset is considered an " upgrade. "

They can introduce new features.

They are only released quarterly.

A media manager always writes RMAN requested backups to tape.

A media manager is required to create RMAN image copies.

A media manager is required to create RMAN proxy copies.

The media manager layer (MML) routines provided by Oracle support any vendors ' media management products.

By default, a request for a proxy copy may result in a backup set being created.

They can view data from any data dictionary view or dynamic performance view.

They can drop any tablespace.

They can view data from any user-defined tables.

They can create any table.

They cannot create restore points.

They cannot drop tablespaces.

A DBA must specify either a redundancy retention policy or a recovery window retention policy. B)A target database ' s persistent RMAN configuration settings are always synchronized automatically with the RMAN catalog.

Backups older than the recovery window retention policy are always deleted automatically if the backup location has insufficient space.

Backups written to the fast recovery area (FRA) that are obsolete based on the redundancy retention policy can be deleted automatically to free space.

A target database ' s persistent RMAN configuration settings are always stored in the target ' s control file.