1z0-083 Practice Exam Questions with Answers Oracle Database Administration II Certification

a General Purpose database template with default memory allocation

a Data Warehouse database template, with t he dedicated server mode option and AMM enabled

a General Purpose database template, with t he shared server mode option and Automatic Memory Management (AMM) enabled

a default database configuration

SYSsessions,regardlessoftherolesthataresetinthesession

SYSTEMsessions,regardlessoftherolesthataresetinthesession

SCOTT sessions, only if the MGR role is set in the session

SCOTT sessions, only if the MGR role is granted to SCOTT

SCOTTsessions,becauseheistheownerofthetable

SYSTEM session, only if the MGR role is set in the session

It can contain a single application

Two application containers can share an application seed PDB.

It must have an application root PDB.

An application PDB can belong to multiple application containers.

It must have an application seed PDB.

It can contain multiple applications.

It fails because Data Pump cannot be container.

It creates a full export of the root

It creates a full export of the root

It creates a full export of only the used while connected to the root container and PDB1. container and all PDBs. container and all open PDBs. root container.

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.

when free space in a dictionary managed tablespace falls below a specified percentage

when free space in a locally managed tablespace falls below a specified percentage

when the total number of locked user account exceeds a specific value

when the number of logons per second exceeds a specific value

when a resumable statement is suspended

when the total number of logons exceeds a specific value

to switch an existing Oracle Database home to a newer release of Oracle software on the same server

to switch to a read-only Oracle home

to switch back to the previous Oracle home as part of a rollback operation

to switch the Oracle Database home when using a centralized Rapid Home Provisioning server

to switch to a patched Oracle Database home Answer: CE

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open PDBs except PDB$SEED.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to a PDB opened in read/ write mode gathers object statistics for that PDB.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics only in CDB$ROOT.

System statistics can be gathered only while connected to CDB$ROOT.

Executing DBMS_STATS.GATHER_DATABASE_STATS while connected to CDB$ROOT gathers object statistics in all open pluggable databases (PDBs)

Stateless alerts can be cleared manually.

Stateless alerts are automatically cleared after one day.

Stateful alerts are purged automatically from the alert history after one day.

Stateless alerts can be purged manually from the alert history.

Stateful alerts must be cleared by a DBA to resolve the problem identified in the alert.

The statistics_level parameter is set to all when any of the PDBs is reopened.

The statistics_level parameter is set to all only for PDB2 when it is reopened.

The statistics_level parameter is set to all when the root database is restarted.

The statement is ignored because there is no SPFILE for a PDB.

FLASHBACK DATABASE

FLASHBACK TABLE

FLASHBACK VERSION QUERY

FLASHBACK DATA ARCHIVE

FLASHBACK TRANSACTION

It is not supported for image copies.

It is only supported for backups to tape via the media management interface.

Duplex backups can be performed on either disk or media, but cannot be performed on media and disk simultaneously.

Duplex backups can contain only data files and control files.

For performing duplexed backups, the parallelism for the device must be set equal to the number of copies.

By default, AWR snapshots are taken every 60 minutes.

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

By default, AWR snapshots are retained for 7 days.

The taking of AWR snapshots can be disabled.

AWR data is stored in the SYSTEM tablespace.

Online Redo Log backups can be created while connected to CDB$ROOT

Control file backups can be created while connected to CDB$ROOT.

The BACKUP TABLESPACE command can back up a pDB tablespace even if RMAN is connected to CDB$ROOT.

Archived Redo Log backups can be created while connected to PDB

Control file backups can not be created while connected to a PDB

SBT tape compression can be used even if no RMAN compression is configured.

Any backup set written to the SBT device in this configuration can contain a maximum of two backup pieces.

Any backup written to the SBT device in this configuration can contain a maximum of two backup sets.

SBT tape compression and RMAN backup compression should be used in parallel.

The SBT device should be configured to use PARALLELISM 2 to allow both tape drive to be used simultaneously.

Use DBCA to create a template from the existing database to contain the database structure with data files and then use the same template to create the database in the new location.

Use Database Configuration Assistant (DBCA) to create a template from the existing database to contain the database structure.

Use DBCA to create a template from the existing database to contain the database structure and then manually copy the data by using Oracle Data Pump.

Create the database by using the CREATE DATABASE . . . command and manually import data by using Data Pump.

It can recommend semantic changes to SQL statements.

It prevents performance regressions for SQL statements when changes are made.

It checks each query being analyzed for missing or stale statistics.

It considers all SQL statements being analyzed by the advisor task as a group.

It only recommends syntactic changes to SQL statements.

redo logs

control files

all data dictionary metadata

user-defined PL/SQL packages

temporary tablespaces

mandatory Oracle-supplied PL/SQL packages

undo tablespaces

Duplication can be done by having the auxiliary database instance pull backup sets from the target database instance.

A connection to an auxiliary instance is always required.

A subset of the target database can be duplicated.

A new DBID is always created for the duplicated database.

A connection to the recovery catalog instance is always required.

A backup of the target database is always required.

Duplication can be done by having the target database instance push copies to the auxiliary database instance.

An application root clone gets created automatically.

The upgrade can be performed when connected either to CDB$ROOT or to PDB$SEED.

After an application upgrade, the application container's PDBs remain synchronized with the existing application root.

The upgrade must be performed when connected to CDB$ROOT.

An application name and version number must be specified to upgrade the application.

After an application upgrade, the application container's PDBs are automatically synchronized with the application root clone.

Application-common Transparent Security Data Protection (TSDP) policies can be created only if all the PDBs in the application container are closed.

Application-common TSDP policies are always container specific.

Application-common OLS policies can be created only if all the PDBs in the application container are closed.

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

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

It requires installation of Oracle Universal Installer.

It supports Rolling Patching.

It must be invoked as the user that owns the software being patched.

It is a Java-based utility for applying patchsets.

It is platform independent.

It can be used to apply interim patches to the Grid Infrastructure and Database Home combination.

PDB-level resource plans can limit uncommitted UNDO per consumer group.

A PDB-level resource plan can limit session PGA memory.

A CDB-level resource plan can limit PDB UNDO use.

A CDB-level resource plan can limit session CPU utilization.

A CDB-level resource plan is mandatory when using PDB-level resource plans.

A CDB-level resource plan can limit PDB CPU utilization

1,3,5,7

3,4,1,6,8

1,3,5,6,7

1,5,6

2,5,6

Any PDB not specified in the plan will be unable to execute statements in parallel.

PDB3 can use all available parallel execution processes at times.

PDB1 is always limited to 40% of the available system resources regardless of demand.

Any PDB notspecified in the plan will be able to use a maximum of 16.5% of the available system resources.

PDB3 is guaranteed to receive at least 20% of the available system resources if there is enough demand.

PDB2 is guaranteed at least 25% of the available parallel execution processes if there is enough demand.

FULL redaction is active on the SAL column

RANDOM redaction is active on the MGR column

RANDOM redaction is active on the HIREDATE column

PARTIAL redaction is active on the MGR column.

PARTIAL redaction is active of the HIREDATE column.

They can be retained forever.

They are always created automatically.

They are always created manually.

They are generated if STATISTICS LEVEL is set to TYPICAL.

They are generated if STATISTICS LEVEL is set to BASIC.

They are generated if STATISTICS LEVEL is set to ALL.

using Database Replay

using SQL Developer

using Oracle Data Pump

using operating system file copy utilities

using Database Upgrade Assistant

using the CREATE TABLE AS SELECT SQL statement

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

APDB snapshot can be a full copy of a source PDB.

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

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

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

It can only be launched from the command line interface.

It can be launched from both the command line and the Universal Installer (OUI) interfaces.

It can be used to create container databases and non-container databases.

It can be used to change the character set of an existing database.

It can be used to convert a non-container database to a container database.

RMAN must be connected to the target database instance and the auxiliary instance.

A most recent backup set of the PROD database must exist.

Flashback must be enabled for the PROD database.

The target database must be in MOUNT state.

CDB1, PDB$SEED, PDB1, and PDB2

PDB$SEED, PDB1, and PDB2 only

CDB1 and PDB$SEED only

CDB1, PDB1, and PDB2 only

CDB1, PDB$SEED, and PDB1 only

After the change, only a common user with the required privilege can create an undo tablespace in CDB&ROOT.

Any new PDB and existing PDBs are automatically configured to use the default undo tablespace in CDB$ROOT.

After the change, only one undo tablespace can exist in CDB$ROOT.

After the change, any user with the required privilege can create an undo tablespace in the PDBs.

Undo tablespaces existing in PDBs must be dropped before the change.

After the change, each existing PDB has to be reopened for the new undo mode to take effect.

AWR snapshots can be created in CDB$ROOT.

ADDM can run in a nonroot container.

AWR reports can be generated while connected to any container.

All AWR data is stored in the CDB$ROOT SYSAUX tablespace.

AWR snapshots can be created in a PDB.

No AWR data is stored in the CDB$ROOT SYSAUX tablespace.

It can be created from a non-CDB.

It can contain only one PDB$SEED, which is created when the CDB is created.

It can have local users with the same name in different PDBs.

It can contain only one Application Container seed, which is created when the Application Container is created.

It can be created by cloning an existing CDB.

It can have any number of pluggable databases (PDBs) limited only by space availability.

It contains predefined common roles in both the root and the seed.

A direct upgrade can be performed only from the immediately preceding Oracle Grid Infrastructure version.

The newer version is installed in a separate Oracle Grid Infrastructure home on the same server as the existing version.

An existing Oracle base can be used.

The upgrade process will automatically install all mandatory patches for the current version of Oracle Grid Infrastructure.

Existing Oracle Database instances must be shut down before starting the upgrade.

Only the grid user can perform the upgrade.

connecting to the target database and a recovery catalog to execute the duplicate command

creating a password file for an auxiliary instance

connecting to an auxiliary instance

matching the database identifier (DBID) of the source database and the duplicate database

creating an SPFILE for the target database

They are never considered obsolete by RMAN.

They can optionally be written to a fast recovery area (FRA).

All archive logs are retained after an archival backup is taken, until the next archival backup is taken of the same database.

Archive logs are retained if they are necessary to allow the database to be recovered to a consistent state when an archival backup is restored.

The SPFILE is included in the archival backup.

Use of a recovery catalog is always required to support the creation and use of archival backups. G)The ARCHIVAL attribute for a backup overrides the RMAN retention policy.

when free space in a dictionary managed tablespace falls below a specified percentage

when free space in a locally managed tablespace falls below a specified percentage

when the total number of locked user account exceeds a specific value

when the number of logons per second exceeds a specific value

when a resumable statement is suspended

when the total number of logons exceeds a specific value

Add the FILE_NAME_CONVERT clause to the statement and set the PDB_FILE_NAME_CONVERT parameter.

Add only the CREATE_FILE_DEST clause to the statement.

Set only the PDB_FILE_NAME_CONVERT parameter.

Set the PDB_FILE_NAME_CONVERT parameter and enable OMF.

Enable only OMF.

Add the FILE_NAME_CONVERT clause to the statement and enable Oracle Managed Files (OMF)

It fails because PDB$SEED is in MIGRATE state.

Only CDB$ROOT, PDB$SEED, and PDB1 are upgraded.

Only CDB$ROOT, PDB$SEED, and PDB2 are upgraded.

It fails because PDB2 is not in UPGRADE state.

CDB$ROOT, PDB$SEED, PDB1, and PDB2 are upgraded.

Only CDB$ROOT and PDB$SEED are upgraded.

Data files with a high value in V$BACKUP_ASYNC_IO.SHORT_WAITS are a potential performance bottleneck when asynchronous I/O is used.

If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then read I/O is a likely bottleneck.F

If an RMAN BACKUP VALIDATE command takes noticeably less time than an actual backup, then write I/O is a likely bottleneck.

If an RMAN BACKUP VALIDATE command takesroughly the same time as an actual backup, then both read and write I/O are likely bottlenecks.

Data files with a high value in V$BACKUP_SYNC_IO.DISCRETE_BYTES_PER_SECOND are a potential performance bottleneck when synchronous I/O is used.

restore and recover database

flashback transaction

flashback database

flashback table and transaction

flashback table

With Automatic Shared Memory Management, the database instance can increase the Large Pool size by reducing the Shared Pool size.

With Automatic Memory Management, the database instance can increase the System Global Area size by reducing the Program Global Area size.

Automatically tuned and resized System Global Area components will always revert to their initial sizes after an instance restart.

Automatic Memory Management must be used together with locking the System Global Area into physical memory.

With Automatic Shared Memory Management, the database instance can increase the Program Global Area size by reducing the System Global Area size.

On Line Transaction Processing systems often use less Program Global Area than Decision Support Systems.

when any archived log from, before, or after the most recent backup is corrupt.

after losing all copies of the control file

after losing an archived log from after the most recent backup

after losing an archived log from before the most recent backup

after losing the SYSTEM tablespace

If a row lock is held by a nonexistent transaction, the block containing the row is media corrupt.

DB_BLOCK_CHECKING=TRUE causes a check sum to be added to each data block to help detect physical or media corruption.

A media corrupt block is one where the block is not formatted correctly.

The ANALYZE TABLE VALIDATE STRUCTURE CASCADE command verifies that each table row has an index entry pointing to it.

If a row lock is held by a nonexistent transaction, the block containing the row is logically corrupt.

DB_LOST_WRITE_PROTECT=TYPICAL causes extra logging overhead on the standby database.

It is automatically synchronized with its application root PDB when an application is upgraded. B)It cannot be added to an application container after the application container has already been created.

A new application PDB created by cloning an application seed PDB can have an old version of the application installed after cloning completes.

It is automatically synchronized with its application root PDB when an application is installed.

It cannot be dropped from its application container.

A new application PDB created by cloning an application seed PDB can have an up-to-date version of the application installed after cloning completes.

It is not required in an application container.

The RMAN LOG command line clause causes output issued during RMAN command compilation to be written to a log file only.

The RMAN LOG command line clause causes output issued during RMAN command compilation to be written to a log file and to standard output.

RMAN error stacks should be read from the bottom up as that is the order in which errors are generated.

Media Management messages for SBT devices are written to an Oracle trace file.

MAN error stacks should be read from the top down as that is the order in which errors are generated.

All audit records are written to the audit trail in CDB$ROOT .

Application-common unified audit policies defined in an application root must be manually synchronized by each application PDB contained in the application root.

Fine-grained auditing policies defined in an application root must be manually synchronized by each application PDB contained in the application root.

A common unified audit policy can be created at the CDB level.

A common unified audit policy can be created at the application root level.

An application PDB cannot have a local audit policy.

USER1 can connect to CDB1.

USER1 can connect to APP1_ROOT and APP1_PDB1.

USER1 can connect to APP1_ROOT, APP1_ROOT$SEED, and APP1_PDB1.

USER1 is defined in APP1_PDB2. E) USER1 can connect only to APP1_PDB1.

USER1 can connect only to APP1_ROOT.

It will create ‘$ORACLE_HOME/dbs/cdb1/CDB1/controlfile02.ctl’

It will create ‘/u01/app/oralce/oradata/CDB1/controlfile/controlfile02.ctl’.

It will re-create ‘/u02/app/oracle/fast_recover_area/cdb1/CDB1/controlfile02.ctl’

It will create ‘/u01/app/oracle/product/12.2.0.1/db_1/dbs/snapcf_cdb1control02.ctl’.

It will fail because there is no autobackup of the controlfiles.

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.

It always analyzes all schemas in the database.

It can recommend changes to improve the statistics gathering process.

It can be run only manually.

It runs automatically every night by default. E) It can be run only automatically.

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.

Data file 24 can be recovered while PDB2 is opened.

Data file 24 must be recovered while the CDB is opened.

Data file 24 can be recovered while CDB$ROOT and PDB$SEED are opened.

Data file 24 cannot be recovered while the CDB is opened.

Data file 24 must be recovered while PDB2 is closed.

A PDB can be plugged into a CDB only if both are of the same Oracle Database release.

An unplugged PDB can be plugged into multiple CDBs simultaneously by sharing data files.

A PDB unplugged from a container database (CDB) can be plugged into a different CDB without altering any of its schemas.

A non-CDB can be converted into a PDB.

A PDB in a remote CDB can be accessed transparently thereby aggregating results from local and remote PDBs.

A PDB created from PDB$SEED must be set to READ WRITE after loading data.

A PDB created from PDB$SEED must be set to READ ONLY after loading data.

The inserts on USER1.EMP remain uncommitted when the session connected to PDB2.

The inserts on USER1.EMP were committed when the session inserted a row into USER2. DEPT.

The insert on USER2.DEPT fails because of the active transaction in the parent container.

The insert on USER2.DEPT is a recursive autonomous transaction by the child session and is committed.

The inserts on USER1.EMP were rolled back when the session connected to PDB2

The insert on USER2.DEPT is uncommitted.

The inserts on USER1.EMP were committed when the session connected to PDB2.

It can be used to deploy Grid Infrastructure homes, including Oracle Restart.

It can be used to deploy Oracle Database homes.

It is an Oracle Database service.

It cannot be used to provision applications.

It cannot be used to provision middleware.

It is an Oracle Grid Infrastructure service.

It can be created only by using RMAN.

It always includes all data files, the current control file, the server parameter file, and archived redo logs.

It can be consistent.

It is the only possible backup type for a database in NOARCHIVELOG mode.

It can consist of either backup sets or image copies.

It can be inconsistent.

the backup retention policy

the backup optimization policy

the DB_CREATE_ONLINE_LOG_DEST_n parameter setting

the archived log deletion policy

the DB_RECOVERY_FILE_DEST parameter setting

using guaranteed UNDO retention

It requires Oracle ASMLib to manage Automatic Storage Managerment (ASMl) disks.

It creates one disk group during installation.

It includes both Oracle Restart and Oracle Automatic Storage Management (ASM) software.

Automatic Storage Management (ASM requires that ars groups OSASM and OSDBA be assigned assecondary groups for its installation owner.

It requires the operating system ORACLE_BASDE environment variable to be predefined before installation.

It requires Oracle ASM Filter Drver (ASMFD) to manage Automatic Storage Managemernt (AsM) disks.

Create an application seed, synchronize it with HR_ROOT, and then create the PDB1 application PDB.

Create the PDB1 application PDB and synchronize it with HR_ROOT.

Create the PDB1 application PDB and install HR_APP in it.

Create the PDB1 application PDB and synchronize it with PDB$SEED.

Create an application seed, and install HR_APP in it.

cloning a remote container database in interactive mode

cloning a remote pluggable database in silent mode

relocating a remote pluggable database in interactive mode

relocating a remote container database in silent mode

cloning a remote container database in silent mode

relocating a remote pluggable database in silent mode

relocating a remote container database in interactive mode.

after losing all members of the CURRENT online redo log group

after losing all copies of the control file

after losing an UNDO tablespace that is in use

after losing all members of an INACTIVE online redo log group

after losing a SYSAUX tablespace data file

The movement of all segments to a target tablespace with a higher degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED

Settingthetargettablespacetoread-only

The movement of some segments to a target tablespace with a higher degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED

Setting the target tablespace offline

The movement of some blocks to a target tablespace with a lower degree of compression, on a different storage tier, when the source tablespace exceeds TBS PERCENT USED Correct

2,4,5,6

1,2,3,4,5,6

1,2,4,5

2,4,5

1,3,4,5

It succeed

It fails because no parallel channels are allocated for the auxiliary databa

It fails because connection to the AUXILIARY instance must be as SYSD

Itsucceeds only if the target database is greater than 40

No catalogued backup of the TARGET is used to duplicate the databa

SQL statements performing many physical I/Os can always have their performance improved by creating indexes.

The solution that best optimizes one SQL statement can degrade the performance of others.

SQL statements doing joins always do more physical I/O than single table queries.

Poorly performing SQL statements can be tuned automatically by the Oracle server.

SQL statements doing only logical reads never require tuning because they do no physical I/O.

creating a disk group using the CREATE DISKGROUP SQL statement

creating a database service using DBMS_SERVICE.CREATE_SERVICE

creating a database service using Oracle Database Configuration Assistant (DBCA)

creating a database using the CREATE DATABASE SQL statement

creating an Oracle Database service by modifying the SERVICE_NAMES parameter

creating an Oracle Automatic Storage Management (ASM) instance with ASM Configuration Assistant (ASMCA)

It will return an error because creation of a local role is not allowed in CDB$ROOT.

ROLE1 will be created only in CDB$ROOT.

It will return an error because common roles must start with C##.

ROLE1 will be created only in CDB$ROOT and APP1_ROOT.

ROLE1 will be created in CDB$ROOT, PDB1, APP1_ROOT, and APP1_PDB1.

Data Recovery Advisor can proactively check for failures.

Using the Data Recovery Advisor LIST FAILURE command always requires that the database for which failures are to be listed is in MOUNT state.

ata Recovery Advisor can be used if a database is in the NOMOUNT state.

A failure can be closed only if the database is in MOUNT state.

Data Recovery Advisor can be used if a database is closed.

To use Flashback Data Archive, users must have unlimited quota on the Flashback Data Archive tablespace.

To enable Flashback Data Archive for a table, it is mandatory to have a default Flashback Data Archive for a database

While enabling Flashback Data Archive for a table, if no name is provided for Flashback Data Archive, it is enabled using the default Flashback Data Archive.

A table enabled for Flashback Data Archive cannot be dropped unless Flashback Data Archive is disabled or disassociated first.

Flashback Data Archive prevents flashback queries from getting a snapshot-too-old error.

It is used in both clustered and non-clustered environments.

You can add and remove components from an Oracle Restart configuration with Server Control (SRVCTL) commands.

It runs from the Oracle Grid Infrastructure home.

If you shut down a database instance with SQL*Plus, Oracle Restart interprets this as a database failure and attempts to restart the instance.

The Server Control (SRVCTL) utility can be used to start and stop Oracle Restart.

It can manage Oracle Database instances, Oracle Net Listeners, and Oracle Automatic Storage Management instances.

The root password cannot be specified in a response file.

The sudo password must be specified in a response file.

orainstRoot.sh can be executed automatically by the Database installer by using sudo or root credentials.

root.sh can be executed automatically by the Database installer only if it is provided with root credentials.

root.sh can be executed automatically by the Database installer only by using sudo credentials.

It will create a multitenant container database (CDB) with only the root opened.

ItwillcreateaCDBwithrootopenedandseedreadonly.

It will create a CDB with root and seed opened and one PDB mounted.

It will create a CDB that must be plugged into an existing CDB.

ItwillcreateaCDBwithrootopenedandseedmounted.

It cannot be backed up manually as a binary copy.

It gets backed up automatically by RMAN as a trace file containing SQL statements for control file re¬creation when a database backup occurs.

It can be backed up manually as a binary copy.

It can get backed up automatically as a binary copy.

It gets backed up automatically by RMAN when the BACKUP SPFILE command is used.

It can be backed up manually as a trace file containing SQL statements for control file recreation.

Compare Period ADDM report

AWR Compare Period report

Active Session History (ASH) report

Taking a new snapshot and comparing it with a preserved snapshot.

RMAN uses the pull method to restore files using image copies

RMAN uses the push method to transfer image copies

RMAN uses the push method to transfer backup sets

RMAN uses the pull method to restore files using backup sets

It succeeds and creates multisection backup sets that are used for active database duplication.

It fails because there is no connection to a recovery catalog.

It succeeds only if the target database is in MOUNT state.

It fails because no parallel channels are allocated for the auxiliary database.

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.