Free Oracle 1z0-182 Practice Exam with Questions & Answers

In the SPFILE and PFILE

In the SPFILE and memory

Only in memory

In the SPFILE, PFILE, and memory

Only in the SPFILE

DB_32K_CACHE_SIZE must be less than DB_CACHE_SIZE.

DB_32K_CACHE_SIZE must be set to a value that can be accommodated in the SGA.

The operating system must use a 32K block size.

DB_32K_CACHE_SIZE should be set to a value greater than DB_CACHE_SIZE.

The /u02 file system must have at least 100G space for the datafile.

COMMON Unified Audit Policies can only be created at CDB level to monitor DBA operation at any level.

At the CDB level.

At the Application Root level of an Application Container.

At any level by using the COMMON option in the policy.

At the PDB level if the policy is created by a COMMON user.

It is a file-based repository held outside any database.

It is only used for Oracle database diagnostic information.

It is held inside an Oracle database schema.

It can be used for the problem diagnosis of a database when that database’s instance is down.

The ADR base is specified in the DIAGNOSTIC_DEST database parameter.

Instance recovery occurs automatically during the shutdown.

Uncommitted transactions are allowed to continue to the next ROLLBACK.

New connection requests made to the database instance are refused.

Sessions remain connected even if they are not running a transaction.

Uncommitted transactions are allowed to continue to the next COMMIT.

A migrated row results in an update to any index on the table to point the row ID in the index to the row’s new location.

Update statements can result in one or more migrated rows.

Update statements can result in one or more chained rows.

Row pieces of a chained row must always reside in different blocks.

Insert statements can result in a migrated row.

You can drop a PDB as long as it is not the PDB seed.

You cannot drop a source PDB of a refreshable PDB.

You can drop an application root along with the associated PDBs.

When the relocation of a PDB is finished, the source PDB must be dropped.

All trace files contain error information that requires contacting Oracle Support.

They can be written by server processes to a file system.

They can be written by background processes to a file system.

Trace file names are based on the database name concatenated with a sequential number.

They can be written by server processes to the Fast Recovery Area (FRA).

Connect Time Failover requires the use of Transparent Application Failover (TAF).

Source Routing requires the use of encrypted connections.

Connect Time Failover requires the connect string to have two or more listener addresses configured.

Load Balancing requires the use of a name server.

Load Balancing can balance the number of connections to dispatchers when using a Shared Server configuration.

A database link can be created only between two Oracle databases.

Private database link creation requires the same user to exist in both the local and the remote databases.

A public database link can be created only by SYS.

A database link created in a database allows a connection from that database's instance to the target database's instance for selecting schema data.

A public database link can be used by any user allowing remote database instance connection for selecting schema data.