1z0-083 Oracle Database Administration II Questions and Answers

V$SESSION_EVENT

V$SESSTAT

V$SESSION_WAIT

V$SESSION_WAIT_CLASS

V$SESSION

RMAN can always repair corrupt blocks.

Flashback commands help with repairing physical errors.

The ADR can store metadata in an Oracle Database repository.

The Automatic Diagnostic Repository (ADR) has a separate home directory for each instance of each Oracle product that is installed and uses it.

The ADR command-line utility (ADRCI) can package incident information to send to Oracle Support.

The Data Recovery Advisor uses the ADR.

The valid time columns employee_time_start and employee_time_end are automatically created.

Thesamestatementmayfilteronbothtransactiontimeandvalidtemporaltimebyusingthe AS OF TIMESTAMP and PERIOD FOR clauses.

The valid time columns are not populated by the Oracle Server automatically.

The valid time columns are visible by default when the table is described.

Setting the session valid time using DBMS_FLASHBACK_ARCHIVE.ENABLE_AT_VALID_TIME sets the visibility for data manipulation language (DML), data definition language (DDL), and queries performed by the session.

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.

Pre-existing backups of the database to be duplicated are required for the "push" method of duplication.

Pre-existing backups of the database to be duplicated are required for the "pull" method of duplication.

Pre-existing backups of the database to be duplicated are always used if they exist.

Image copies can be used to duplicate the active database.

The active database must be duplicated while in OPEN state.

No connection to the recovery catalog is required for active database duplication.

Backup sets can be used to duplicate the active database.

Plugging the application root into a different CDB plugs in all its application PDBs.

The application root of an application container should be plugged into the other CDB before its application PDBs are plugged in.

Application PDBs in the application container must be unplugged before the application root is unplugged.

Unplugging the application root from a CDB unplugs all its application PDBs.

It requires only local UNDO mode in the database where the application container will be unplugged.

It requires local UNDO mode in both container databases.

Create SQL plan directives for each of the regressed statements.

Use The SQL Tuning Advisor for each of the regressed statements.

Create an adaptive execution plan for each of the regressed statements

Use the SQL Access Advisor for each of the regressed statements.

DBUA must be launched from the target Oracle Home.

Multiple databases with the same ORACLE_HOME can be upgraded simultaneously.

A whole database backup must exist before upgrade.

The Pre-Upgrade Information Tool script is executed by DBUA.

All pluggable databases are automatically upgraded as part of a container database upgrade.

The database must be opened in read-only mode.

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.

To use it, Flashback Database must be enabled.

A block being recovered is not accessible.

It cannot repair logical corruption.

It can be performed on noncorrupt blocks.

The target database for which one or more blocks are to be recovered must be in the OPEN state.

The data file containing the block being recovered remains online.

All AWR tables belong to the SYSTEM schema.

The AWR data is stored in memory and in t he database.

The snapshots collected by AWR are used by the self-tuning components in the database

AWR computes time model statistics based on time usage for activities, which are displayed in the v$SYS time model and V$SESS_TIME_MODEL views.

AWR contains system wide tracing and logging information.

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.

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.

the data dictionary in CDB$ROOT

the log writer process (LGWR)

SYSAUX tablespaces

temporary tablespaces

the Process Monitor Process (PMON)

undo tablespaces

PDB1 data files already exist in the correct location.

DBMS_PDB.CHECK_PLUG_COMPATIBILITY must be run in CDB1 before executing the command.

PDB_FILE_NAME_CONVERT must be set before executing the command.

/u01/app/oracle/oradata/pdb1.xml does not contain the current locations of data files for PDB1.

PDB1 must be dropped from CDB1.

the Optimal Flexible Architecture (OFA) compliant path to store Oracle software and configuration files.

the location of Oracle Net Services configuration files

the list of a disk group names to be mounted by an Oracle Automatic Storage Management (ASM) instance at startup

default directories for temporary files used by temporary tablespaces

the temporary disk space used by Oracle Installer during installation

the maximum number of database files that can be opened by a database instance

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 used to patch existing Oracle software installations.

It can be used only on nodes with Oracle Grid Infrastructure installed.

It can be used to create a single-instance Oracle Database in an already-installed Oracle home. D)It can be used to deploy new homes without disrupting active databases.

It can be used to create templates of Oracle homes as gold images of only Oracle databases.

It can be used to upgrade only single-instance databases running on Oracle Restart.

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.

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.

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

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

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

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

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

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

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

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.

It requires Oracle ASMLib to manage Automatic Storage Management (ASM) 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 O/S groups OSASM and OSDBA be assigned as secondary groups for its installation owner.

It requires Oracle ASM Fitter Driver (ASMFD) to manage Automatic Storage Management (ASM) disks.

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

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.

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.

The sudo password can be specified in a response file.

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

The sudo password must be specified in a response file.

The root password cannot be specified in a response file.

All historical data older than two years, if any, is purged from the flashback archive FDA1.

An error is returned because the retention period cannot be reduced.

All the flashback data archives are purged and the subsequently created flashback archives are maintained for two years

All historical data older than two years, if any, is archived to flashback logs and the flashback archive is set to new retention time.

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.

SGA_MIN_SIZE cannot be set for a PDB.

Setting SHARED_POOL_SIZE for a PDB guarantees a minimum amount of Shared Pool memory for that PDB.

Setting SGA_TARGET for a PDB guarantees a minimum amount of SGA memory for that PDB.

The SHARED_POOL_SIZE setting for a PDB can be up to 80% of the SHARED_POOL_SIZE setting of the root container.

Setting DB_CACHE_SIZE for a PDB guarantees a minimum amount of Database Buffer Cache memory for that PDB.

The SGA_TARGET setting for a PDB cannot exceed 50% of the SGA_TARGET value of the root container.

TheC# # B_ADMIN user can perform all back up and recovery operation susing RMAN only.

The C # # C_ADMIN user can perform the data guard operation with Data Guard Broker.

The C # # A_ADMIN user can perform wallet operations.

The C # # D_ADMIN user can perform backup and recovery operations for Automatic Storage Management (ASM).

The C # # B_ADMIN user can perform all backup and recovery operations using RMAN or SQL* Plus.

It recompiles all stored PL/SQL code by using utlrp.sql.

It empties the RECYCLE BIN.

It performs prerequisite checks to verify if the Oracle database is ready for upgrade.

It sets all user tablespaces to “read-only” before starting the upgrade.

It removes the AUDSYS schema and the AUDIT_ADMIN and AUDIT_VIEWER roles

It increases tablespace size, if required, to meet upgrade requirements.

to generate an XML metadata file that describes a non-CDB Oracle 12c database so that it can be plugged in as a PDB

to generate an XML metadata file from any unplugged PDB

to determine whether an XML file describes a PDB that can be plugged into the CDB in which you run the procedure

to generate a . pdb archive file for any PDB in the current CDB

to generate an XML metadata file that describes the current plugged-in PDB

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

A table's constraints must be disabled before issuing the flashback.

The FLASHBACK ANY TABLE system privilege or the FLASHBACK object privilege must be granted to the user performing the flashback.

Row Movement must be enabled on the table being flashed back.

A table's indexes must be set to unusable before issuing the flashback.

The FLASHBACK ANY TABLE system privilege or the FLASHBACK object privilege must be granted to the table owner.

The ORA_ARCHIVE_STATE column may only be queried by users with the DBA role set.

The ORA_ARCHIVE_STATE column is only displayed if it is referenced in the column select list of a query

The ROW ARCHIVAL VISIBILITY session parameter defaults to active rows.

The ORA_ARCHIVE_STATE column may only be updated by users with the DBA role set.

The ORA_ARCHIVE_STATE column is updated in an overnight maintenance job based on activity tracking.

Control file backups can be created while connected to the root container.

Archived Redo Log backups can be created while connected to an application root CDB.

Control file backups can be created while connected to a nonroot container.

Online Redo Log backups can be created while connected to the root container.

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

RMAN can recover tables owned by the SYSTEM user.

RMAN can recover tables owned by the SYS user.

RMAN can recover tables in the SYSTEM tablespace.

RMAN always uses an auxiliary instance.

RMAN can recover a table after a DDL operation has altered the table structure.

RMAN can recover tables in the SYSAUX tablespace.

RMAN can recover tables in a standby database.

Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.

Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.

Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE argument set to No.

Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE arguments set to Yes.

Re-createthepasswordfileintheOracleDatabase12cformat. Correct

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

PDB2 will be opened READ WRITE.

PDB1 will be opened READ WRITE.

PDB1 will be MOUNTED.

PDB$SEED will be opened READ ONLY.

PDB$SEED will be MOUNTED

PDB2 will be MOUNTED.

Increase the size of tape I/O buffers.

Disable FORCE LOGGING for the database.

Increase the size of the database buffer cache.

Enable asynchronous disk I/O.

Increase the level of RMAN multiplexing.

It performs a shutdown and then a restart of all processes in both Oracle Grid Infrastructure and Oracle Database home during the patching process.

It must be invoked by a user with root user privileges.

Patches are applied via opatchauto.

Users must always input patch plans to opatchauto.

It requires the Oracle Grid Infrastructure and Oracle Database instances to be shut down before being invoked.

It applies patches in nonrolling mode by default.

It is used to apply interim patches to Oracle Grid Infrastructure and Oracle Database home combinations.

Flashback logs are written sequentially, and are archived.

Flashback Database uses a restored control file to recover a database.

The Oracle database automatically creates, deletes, and resides flashback logs in the Fast Recovery Area.

Flashback Database can recover a database to the state that it was in before a reset logs operation.

Flashback Database can recover a data file that was dropped during the span of time of the flashback.

Flashback logs are used to restore to the blocks' before images, and then the redo data may be used to roll forward to the desired flashback time.

PDB1_C2_SRV will be created but not started.

PDB1 will be created in CDB2 and automatically opened.

PDB1_C1_SRV in CDB1 will be renamed PDB1_C2_SRV.

PDB1 will be created in CDB2 and left in MOUNT state.

PDB1_C2_SRV will be created and started automatically.

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

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

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

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

System statistics can be gathered only while the CDB is in MOUNT state.

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

V$SESSION_EVENT displays all waits for all past and existing sessions if the wait has occurred at least once for a session.

V$SERVICE_EVENT displays all waits for all services if the wait has occurred at least once for a service.

V$SESSION_WAIT _CLASS displays waits broken down by wait class only for waiting sessions.

V$SESSION_WAIT and V$SESSION both contain details of the event on which a non-waiting session last waited.

V$SESSION_EVENT displays all waits for all past sessions if the wait has occurred at least once for a session.

V$SESSION_WAIT and V$SESSION both contain details of the event on which a session is currently waiting.

The NOREDO clause must be used if the backups of the database being duplicated were taken when the database was in NOARCHIVELOG mode.

The UNDO TABLESPACE clause is always required when no connection exists to the TARGET instance.

RMAN “pushes” the backups of the database to be duplicated over the network to the auxiliary instance.

The NOREDO clause can be used if the backups of the database being duplicated were taken when the database was in ARCHIVE LOG mode.

RMAN SBT-based backups of the database to be duplicated can be used by the auxiliary instance.

The UNDO TABLESPACE clause is always required when no connection exists to the recovery catalog and the TARGET database is closed.

The UNDO TABLESPACE clause is always required when no connection exists to the recovery catalog and the TARGET database is opened.

Tune individual SQL statements using the SQL Tuning Advisor.

Identify poorly tuned SQL statements using Automatic Database Diagnostic Monitor.

Test the application as a whole using tuned SQL statements.

Test tuned SQL statements one at a time for all statements in the application.

Identify poorly tuned SQL statements using the SQL Tuning Advisor.

Tune SQL statements as a group using the SQL Tuning and SQL Access Advisors.

user-managed backups of data files and control files

flashback logs

RMAN backups that are obsolete

archived redo log files that have multiple copies in a different archive location

It uses multisection backup.

It uses parallelization for the backup set.

It uses asynchronousI/O for the backup.

It creates compressed backup sets.

A Lockdown profile created from a base Lockdown profile is always automatically modified if the profile on which it is based is modified.

A PDB Lockdown profile can be created in an application root.

A Lockdown profile created from a base Lockdown profile is never automatically modified if the profile on which it is based is modified.

A PDB Lockdown profile can be created in a regular PDB.

A PDB Lockdown profile can be created in CDB$ROOT .

by performing emergency monitoring using Real-Time Automatic Database Diagnostic Monitor (ADDM) to fetch data directly from SGA for analysis

by running ADDM to fetch information from the latest Automatic Workload Repository (AWR) snapshots

by using Active Session History (ASH) data and performing hang analysis

by running ADDM in diagnostic mode

They are generated if STATISTICS_LEVEL is set to TYPICAL.

They are always created manually.

They are always created automatically.

They are generated if STATISTICS_LEVEL is set to BASIC.

They are generated if STATISTICS_LEVEL is set to ALL.

They can be retained forever.

A base recovery catalog should exist.

The owner of VPC cannot own recovery catalog.

At least one target database should be registered in the recovery catalog.

The register database privilege should be granted to the virtual catalog owner.

The recovery_catalog_owner role should be granted to the virtual catalog owner.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using RMAN while connected to PDB1.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using SQL while connected to PDB1.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using SQL while connected to CDB$ROOT.

Execute FLASHBACK PLUGGABLE DATABASE PDB1 TO RESTORE POINT R1by using RMAN while connected to CDB$ROOT.

This cannot be done due to the lack of a clean restore point.

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.

It includes the Oracle Preinstallation RPM.

From Oracle Database 18c, a single RPM can be used to install only Oracle Database Server for a single instance.

It requires an Unbreakable Linux Network (ULN) subscription.

It performs a software-only Oracle Database installation.

It uses a service configuration script to create a single-instance database as part of the installation.

The UNDO TABLESPACE clause is always required when no connection exists to the recovery catalog and the TARGET database is closed.

RMAN disk-based backups of the database to be duplicated can be used by the auxiliary instance.

The UNDO TABLESPACE clause is always required when no connection exists to the TARGET instance.

The UNDO TABLESPACE clause is never required.

RMAN "pushes" the backups of the database to be duplicated over the network to the auxiliary instance.

using RMAN stored scripts

creating encrypted backups

creating customized reports about a single database's backups

using the REPORT SCHEMA command to list a database's data files and tablespaces at times in the past

using the KEEP FOREVER clause with the BACKUP command

using the REPORT SCHEMA command to list a database's current data files and tablespaces

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

The Transparent Data Encryption (TDE) keystore is backed up using RMAN.

Vendor-specific media management software can be used for making encrypted RMAN backups to media.

The BACKUP BACKUPSET command can encrypt and decrypt backup sets.

Image copies can be encrypted.

Keystore-based encryption is the default mode for RMAN backup encryption.

Backup encryption can be enabled selectively for specific tablespaces.

ADDM can recommend shrinking the buffer cache.

ADDM can recommend extending the buffer cache.

By default, MMON creates an AWR snapshot every 30 minutes.

ADDM performs its analysis only when a DBA requests it.

By default, AWR snapshots are automatically purged after eight days.

AWR snapshots must be deleted when no longer required by ADDM.

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.

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.

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

Create the PDB1 application PDB and synchronize it with HR_ROOT.

Create the PDB1 application PDB and install HR_APP in it.

Create an application seed, and install HR_APP in it.

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

Databases from the RC12C catalog are implicitly unregistered if the RC11 catalog has registered databases with same name.

Recovery catalog is resynchronized with the control files of the registered databases.

Imported databases are unregistered from the RC11 catalog.

Local and global stored scripts that have the same name as existing scripts in the RC12C catalog are automatically renamed.

All databases registered in the RC11 catalog are registered in the RC12C catalog.

after losing a SYSAUX tablespace data file

after losing all members of an INACTIVE online redo log group

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

The ORCL database, the Oracle ASM instances, the +DATA and +FRA disk groups, and the LISTENER are started.

Only the ORCL database instance is started.

Only the ORCL database and the ASM instances are started.

Only the ORCL database instance, the Oracle ASM instance, and the +DATA and +FRA disk groups are started.

Only the ORCL database instance and the +DATA and +FRA disk groups are started.

Fast Recovery Area must be enabled for the database

The EXECUTE privilege must be granted to a user on the DBMS_FLASHBACK package.

Undo retention guarantee must be configured for the database.

A supplemental log must be enabled for the primary key.

A supplemental log must be enabled for the primary key.

The response file can specify the path of the sudo program.

The response file must contain the root or sudo password.

Silent install always runs operating scripts automatically.

The response file can specify the root or sudo password.

The installer will prompt for the root or sudo password.

log writer performance

database writer performance

general operating system health

SQL statements

database instance memory management and sizes

It is integrated with the SQL Access Advisor.

It predicts the impact of system changes on SQL workload response time.

It provides before and after execution statistics for each SQL statement in the analysis task

It offers fine-grained analysis of all the SQL statements in the analysis task as a group.

SQL statements that were originally run concurrently are run concurrently by SPA.

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.

Compressed backups cannot have a section size defined.

Compressed backups can be written only to media.

Binary compression adds CPU overhead to backup operations.

Unused blocks below the high water mark are backed up.

Compression can be done only for locally managed tablespaces.

DataisredactedfortheEMP.SALcolumnonlyiftheSCOTTsessiondoesnothavetheMGR role set.

DataisredactedforEMP.SALcolumnonlyiftheSCOTTsessionhastheMGRroleset.

Data is never redacted for the EMP_VW.SAL column.

Data is redacted for the EMP_V.SAL column only if the SCOTT session has the MGR role set.

Data is redacted for the EMP_V.SAL column only if the SCOTT session does not have the MGR role set. Correct

They must be written to media.

They can be written only to disk.

They can be created only by using the COPIES option of a BACKUP command.

They can be created by using the RMAN CONFIGURE command to specify duplexing before taking a backup.

They can be written to media.

Application PDBsthat are subsequently created in the APP1 application container will be cloned from APP1$SEED.

An application seed PDB is created for APP1.

An application root PDB is created for APP1.

A default service is created for the application root APP1.

Application PDBs that are subsequently created in the APP1 application container will be cloned from PDB$SEED.

APP1 can never be unplugged.

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.

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.

It succeeds and needs to be enabled to capture all SQL statements that require either the specified privileges or any privilege granted to the HR_ADMIN or OE_ADMIN role.

It fails because the command does notspecify when the unified audit policy should be enforced.

It succeeds and starts capturing only successful SQL statements for all users who have either the specified privileges or roles granted to them.

It fails because system privileges cannot be granted with roles in the same audit policy.

BACKUP TABLESPACE SYSTEM SECTION SIZE 100M;

BACKUP AS COPY TABLESPACE SYSTEM SECTION SIZE 100M;

BACKUP ARCHIVELOG ALL SECTION SIZE 25M;

BACKUP TABLESPACE "TEMP" SECTION SIZE 10M;

BACKUP TABLESPACE "UNDO" INCLUDE CURRENT CONTROLFILE SECTION SIZE 100M;

BACKUP SPFILE SECTION SIZE 1M;

BACKUP INCREMENTAL LEVEL 0 TABLESPACE SYSAUX SECTION SIZE 100M;