Oracle 1z0-083 - Oracle Database Administration II

Backups can be taken only if a fast recovery area is configured.

Backups can be written only to disk.

Backups can be taken only for data files.

Binary compression cannot be applied to the backup.

Backups can be written only if checksums are stored for each block.

Backups can be written only to media.

By default, the transported database will use Oracle Managed Files (OMF)

Data files can be converted on the destination system.

Data files can be converted on the source system.

A new DBID is automatically created for the transported database.

Databases can be transported between systems with different endian formats.

The password file is automatically converted by RMAN.

to allow database duplication without a connection to the target instance.

to store backup metadata that would cause the controlfile to become too large.

to store backups that would cause the controlfile to become too large.

to report on the database schema at an earlier point in time.

to allow database duplication without a connection to the auxiliary instance.

Data file 24 can be recovered only while connected to PDB2.

Data file 24 can be restored and recovered while connected to CDB$ROOT.

Data file 24 can be restored only while connected to CDB$ROOT.

Data file 24 can be restored only while connected to PDB2.

Data file 24 can be recovered while connected to PDB2.

Data file 24 can be recovered while connected to CDB$ROOT.

It is used to change failure priority only for HIGH or LOW priorities.

It is used to execute the advised repair script.

It is used to change failure priority only for the CRITICAL priority.

It is used to explicitly close the open failures.

It is used to inform the database about the repair after the repair script executes.

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.

The entire PGA is located in the System Global Area (SGA) when using shared servers.

PGA_AGGREGATE_LIMIT is a hard limit on the PGA size for any one session.

The private SQL area (UGA) is located in the System Global Area (SGA) when using dedicated servers.

The private SQL area (UGA) is located in the System Global Area (SGA) when using shared servers.

Sorts and Hash Joins use PGA memory.

It is a set of recommendations by the optimizer to change the access methods used.

It is auxiliary information collected by the optimizer for a SQL statement to eliminate estimation error.

It is a set of recommendations by the optimizer to restructure a SQL statement to avoid suboptimal execution plans.

It is auxiliary information collected by the optimizer for a SQL statement to help use better joins orders.

It is a set of recommendations by the optimizer to create new indexes.

Tablespaces always remain in read/write mode during transportable tablespace operations.

Tablespaces never remain in read/write mode during transportable tablespace operations.

A transportable data pump import can leave a plugged-in tablespace in read-only mode.

Simultaneous data pump jobs can be limited at the pluggable database (PDB) level.

A transportable data pump import can leave a plugged-in tablespace in read/write mode.

An ordinary data pump export of a table with encrypted columns will always encrypt the same columns when imported.

CDB2 must be in shared UNDO mode only.

CDB2 must be in archivelog mode.

CDB1 must be in archivelog mode.

CDB1 and CDB2 must both be in local UNDO mode.

CDB1 must be in shared UNDO mode only.A container database, CDB1, contains a pluggable database PDB1.

CDB1 and CDB2 must be in shared UNDO mode.