Oracle 1z0-083 Oracle Database Administration II Exam Practice Test

Any Recovery Manager (RMAN) recovery catalog must be upgraded manually.

After a manual upgrade, TNSNAMES.ORA entries must be updated to reflect the new ORACLE_HOME.

Time zone files must be upgraded manually using the DBMS_DST PL/SQL package.

The new extended data type capability must be enabled by running the utlrp.sql script

The Oracle Application Express configuration should be updated after upgrading Oracle Database.

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.

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

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

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

It is enabled for all users having SELECT privilege on SH.SALES.

Only successful queries of SH.SALES are written to the audit trail.

It is only enabled for user SH.

Audit records are always stored in an external audit file.

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.

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.

Data Pump full database export and import

cloning the non-CDB as a PDB

replication using GoldenGate

Data Pump transportable tablespaces

Data Pump full transportable database

the DBMS_PDB package

to switch to a patched Oracle Database home

to upgrade an Oracle Database on the centralized Rapid Home Provisioning server

to move an Oracle Database to the centralized Rapid Home Provisioning server

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

to switch to a read-only Oracle home

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 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.

when a character set conversion is required during the upgrade

when multiple pluggable databases in a container database have to be upgraded in a specific sequence

when the target and source database are on the same platform

when the hardware platform needs to be changed as part of the upgrade

when the operating system (OS) needs to be changed as part of the upgrade

Backups must be done incrementally.

Backups must be contained in backup sets.

Backups can be taken only if the database is in ARCHIVE LOG mode.

Backups can be done incrementally.

The database must be registered in an RMAN catalog.

Only consistent backups can be created.

PDB1 and PDB2 are in MOUNT state.

Redo logs are opened.

PDB1 and PDB2 are in READ ONLY state.

CDB$ROOT is in MOUNT state.

PDB$SEED is in READ ONLY state.

FLASHBACK DATABASE

FLASHBACK TABLE

FLASHBACK VERSION QUERY

FLASHBACK DATA ARCHIVE

FLASHBACK TRANSACTION

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.

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.

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

V$SERVICE_EVENT displays wait counts for every wait event for each service even including counts of zero for waits that never occurred.

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

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

V$SESSION_EVENT displays all waits events for those events that have occurred at least once for sessions that have now terminated.

V$SESSION_WAIT_CLASS displays waits broken down by wait class only for terminated sessions.

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.

Stateful alerts must be created by a DBA after resolving the problem.

Stateless alerts can be purged manually from the alert history.

Stateless alerts can be cleared manually.

Stateless alerts are automatically cleared.

Stateful alerts are purged automatically from the alert history

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

Setting DBWR_IO_SLAVES to a non zero value can improve backup performance when using synchronous I/O.

If an RMAN BACKUP VALIDATE command takes noticeably lessthan 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 read I/O is a likely bottleneck.

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.

Setting DBWR_IO_SLAVES to a non zero value can improve backup performance when using asynchronous I/O/

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

to specify a default tablespace in a PDB cloned from another PDB in the same CDB

to exclude all tablespaces except SYSTEM, SYSAUX, and TEMP when plugging in a PDB

to include specific user tablespaces only when relocating a PDB

to specify the list of user tablespaces to include when moving a non-CDB to a PDB

to exclude a temp tablespace when plugging in a PDB

to specify the list of tablespaces to include when creating a PDB from the CDB seed

It is an Oracle Database service

It cannot be used to upgrade Oracle Database homes.

It can be used to provision applications.

It can be used to patch Grid Infrastructure homes containing Oracle Restart.

It can be used to provision middleware.

It is not possible if an archived log is missing.

It is performed automatically after the database is opened; however, blocks requiring recovery are not available until they are recovered.

Setting FAST_START_MTTR_TARGET to a lower value reduces instance recovery time by causing dirty buffers to be written to disk more frequently, thereby reducing the number of I/Os needed during instance recovery.

It is performed by the Recovery Writer (RVWR) background process.

Setting FAST_START_MTTR_TARGET to a higher value reduces instance recovery time by causing The log writer to write more frquently, thereby reducing the number of I/Os needed during instance recovery.

It is performed automatically while the database remains in MOUNT state. Then the database is opened.

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.

All archive redo log files are automatically copied to the duplicate database.

The duplicate database has the same directory structure as the source database.

The duplicate database is created by using the backups created during the execution of

he duplicate command.

The password file and SPFILE for the duplicate database dup1 are created in their respective default locations.

The duplicate database is created without using RMAN backups and prod1 is allowed to remain open during duplication.

DBMS_PDB.CHECK_PLUG_COMPATIBILITY can be run against a PDB archive.

They contain a PDB manifest file and all the data files in uncompressed form for a PDB.

They contain all the data files only in uncompressed form for a PDB.

They must be created using the DBMS_PDB package.

They contain a PDB manifest file and all the data files in compressed form for a PDB.

They contain all the data files only in compressed form for a PDB.

Uncommitted transactions in PDB1 have been rolled back.

PDB1 is closed.

Uncommitted transactions in CDB1 and PDB1 have been rolled back.

CDB1 is shut down.

CDB1 is in MOUNT state

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

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.

backup retention policy

default backup device type

default section size for backups

default destinations for backups

multiple backup device types for a single backup

A backup set may be duplexed with both copies written to disk.

An image copy on disk can be copied to disk.

A backup set may be duplexed with both copies written to sbt.

A backup set may be duplexed so that one copy is written to sbt and the other to disk.

An image copy on disk can be copied to sbt.

An image copy on sbt can be copied to disk.

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

Reduced logical I/O

Reduced virtual memory utilization

Improved Serial Execution performance

Reduced physical I/O

Reduced CPU utilization

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.

1,3,5, 6, 9

1,3, 5, 7, 10

1,2, 5, 7,4, 10

1,3, 5, 6, 10

1,3,5, 6, 10

1,3,5,8, 6, 10

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.

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.

1,3,5,7

3,4,1,6,8

1,3,5,6,7

1,5,6

2,5,6

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 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.

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.

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.

Tables or table partitions can be recovered by using an auxiliary instance only.

Tables or table partitions with a foreign key cannot be recovered.

Tables or table partitions can be recovered only when the database is in mount state.

Tables or table partitions from the system and sysaux tablespaces cannot be recovered.

Tables with not null constraints cannot be recovered.

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.

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.

If no PDB plan is enabled for a pluggable database, then all sessions for that PDB are treated to an equal degree of the resource share of that PDB.

In a PDB plan, subplans may be used with up to eight consumer groups.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups across all PDBs in the CDB.

If no PDB plan is enabled for a pluggable database, then the PDB share in the CDB plan is dynamically calculated.

If a PDB plan is enabled for a pluggable database, then resources are allocated to consumer groups based on the shares provided to the PDB in the CDB plan and the shares provided to the consumer groups in the PDB plan.

Updating client scripts with the new Oracle home.

Resetting passwords to enforce case-sensitivity.

Run OPatch commands from the new Oracle home.

Setting threshold values for tablespace alerts.

Migration to unified auditing.

Upgrading user tables that depend on Oracle-maintained abstract data types.

1,3,5,7

2,5,6

1,5,6

3,4,1.6,8

1,3,5,6,7

all backups prior to 10th of August

all backups prior to 22nd of August

all backups prior to 20th of August

all backups prior to 24th of August

all backups prior to 17th of August

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

oracle will be an owner of the Oracle Inventory.

oracle must be the owner of every Oracle Database installation.

oracle can own an Oracle Database installation but not an Oracle Grid Infrastructure installation.

oracle will be granted the SYSASM privilege when installing the Oracle Database software.

The user account, oracle, and group, oinstall, can be used for all Oracle software installations.

The General Purpose of Transaction Processing templates are most suitable when concurrency and recoverability are key criteria.

Oracle DBCA templates can store only logical structure and not database files.

New templates can only be created by modifying an existing user-created template.

The Data Warehouse template is most suitable when transaction response time is the key criterion.

Oracle DBCA templates can be used to create new databases and duplicate existing databases.

1,3,6

1,2,5

3,4,5

2,3,5,6

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

It can be used to transport data from a non-CDB to a PDB.

It can be used to clone a CDB.

It can be used to transport data between PDBs.

It can be used to transport data from a PDB to a non-CDB.

It can be used to create a new PDB.

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.

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.

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.

The control file is backed up whenever a new tablespace is created.

The server parameter file (SPFILE) is automatically backed up each time the control file is backed up.

The control file is backed up whenever a new table is created.

The control file is backed up whenever an RMAN backup is successfully recorded in the catalog.

It requires the use of fast recovery area (FRA).

The control file is backed up automatically each time the SPFILE is backed up manually.

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.

Flashback logs are not archived.

Flashback logs are maintained in redo log files.

Flashback logs are maintained in the Flash Recovery Area.

Flashback logs are used to maintain Flashback Database related errors.

Flashback logs need to be cleared manually after you disable Flashback Database.

automatically dropping the database link to the remote database if it already exists

opening the cloned PDB

creating a new empty PDB in the local database from PDB$SEED

creating a database link from CDB$ROOT in the local database to CDB$ROOT in the remote system that is to be cloned

creating a database link from CDB$ROOT in the remote database to be cloned to CDB$ROOT in the local database

creating a database link from CDB$ROOT in the local database to the PDB in the remote system that is to be cloned

creating a database link from CDB$ROOT in the remote database to the PDB in the local database

A backup piece can belong to only one backup set.

A data file can be split into multiple sections stored in different backup sets.

A data file can be split into multiple sections stored in different backup pieces in the same backup set.

Blocks from multiple data files can be contained in one backup piece,

A backup set can contain only one backup piece.

A backup set must be written to media.

A backup set must be written to disk.

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.

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

an operating system user to own this installation

the Oracle Inventory group oinstall

an operating system account called grid

a group called dba

the installation of Oracle ASMLIB

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.

Open the CDB instance in restricted mode. In CDB$ROOT, drop the UNDO tablespace. Execute ALTER DATABASE LOCAL UNDO ON in each PDB, and then restart the CDB instance.

Open the CDB instance in upgrade mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON, and then restart the CDB instance.

Open the CDB instance in upgrade mode. In each PDB, execute ALTER DATABASE LOCAL UNDO ON, create an UNDO tablespace, and then restart the CDB instance.

Open the CDB instance in restricted mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON. create an UNDO tablespace in each PDB, and then restart the CDB instance.

Open the CDB in read-only mode. In CDB$ROOT, execute ALTER DATABASE LOCAL UNDO ON, and then change the CDB to read/write mode.

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.

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.

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.

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.

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.

If the password file location changes, then the new location is used automatically by the Oracle Server.

Schema Only accounts can be granted administrator privileges.

All the Oracle-supplied accounts are Schema Only accounts.

Privilege Analysisisincluded in Oracle Enterprise Edition and no longer requires Database Vault. E) Unified Auditing can be configured to audit only events that are issued indirectly by an audited user.

Unified Auditing can be configured to audit only events that are issued directly by an audited user.

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.

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.

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.

redo logs

control files

all data dictionary metadata

user-defined PL/SQL packages

temporary tablespaces

mandatory Oracle-supplied PL/SQL packages

undo tablespaces

The Automatic Database Diagnostic Monitor (ADDM) Compare Period report can compare two consecutive periods.

SQL Performance Analyzer can suggest schema changes.

SQL Performance Analyzer can identify regressed SQL statements.

Database Replay always uses one replay client for all the original database sessions.

Database Replay always uses one replay client for each original database session.

The Automatic Database Diagnostic Monitor (ADDM) Compare Period report can compare two non¬consecutive periods.

The Active Session History (ASH) report is based on wait event samples.

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.

FLASHBACK DATABASE only uses FLASHBACK LOGS to get the database to the desired flashback time.

It requires that the target database be in ARCHIVELOG mode.

FLASHBACK LOGS are archived after a log switch.

A database can be flashed back using SQL*PLUS.

It always generates REDO and UNDO.

Queries and DML have the same FLASHBACK LOG overhead when flashback is enabled for a database.

CDB1_TAB, APP_ROOT_TAB, and APP_PDB1_TAB

CDB1_TAB and APP_PDB1_TAB

CDB1_TAB and APP_ROOT_TAB

CDB1_TAB only

none of the tables, because all three tables will be dropped