Oracle 1z0-497 Oracle Database 12c Essentials Exam Practice Test

Result Cache Background process (RCBG)

AQ Coordinator process (QMNC)

Change Tracking Writer process (CTWR)

Listener Registration process (LREG)

It uses internal infrastructure components, such as XDB and SQL*Net.

It can perform actions outside the database.

It has background tasks and processes that periodically collect information via FTP.

It has two new features: Performance Hub and Composite Active Reports.

It is not supported on Standard Edition (SE) and Express Edition (XE).

Recovery of individual PDBs is not possible, because John did not back up by using RMAN>Backup Pluggable database pdb1 pdb2. However, complete CDB recovery is still possible.

Mike and Tim need to individually take backups of their respective PDBs, because CDB-level backup does not include PDB data dictionary objects.

Mike and Tim do not need to worry, because recovery of individual PDBs is possible.

Recovery of individual PDBs is not possible at all.

The session is terminated after receiving the error and JIM can continue with his transaction.

SCOTT should perform a COMMIT or ROLLBACK to allow JIM to continue with his transaction.

The session is rolled back after receiving the error and JIM can continue with his transaction.

SCOTT has to re-execute the last command in the transaction after he commits the transaction.

A common user cannot have the same name as any local user across all PDBs.

A common user can be created only in the root container.

A local user with the proper privileges can also create a common user.

If a PDB is closed, the common and local users of the PDB are not visible.

A common user with the proper privileges can create a common user by using the CONTAINER=CURRENT clause.

A common user is one that has the same username and authentication credentials across multiple PDBs.

durability

consistency

concurrency

isolation

scalability

manageability

It is ignored by the query optimizer.

It is not used while the index is being rebuilt.

The index cannot be rebuilt, and has to be re-created.

The index is automatically rebuilt when used the next time.

View performance and status information about the database instance.

Start up the database.

Shut down the database.

Create database structures.

Manage users and security.

RMAN> VALIDATE CHECK LOGICAL

RMAN> VALIDATE BACKUP

RMAN> VALIDATE CORRUPT BLOCKS

RMAN> VALIDATE DATABASE

database files and parameter file (initialization parameter file or server parameter file)

System Global Area (SGA) and background processes

a listener process, server processes, and background processes

System Global Area (SGA), server processes, and background processes

database files, System Global Area (SGA), and background processes

1, 2, 3, 4, 5

2, 1, 5, 3, 4

5, 1, 2, 3, 4

2, 3, I, 5, 4

1, 2, 4, 5, 2

Nothing else happens.

The database is mounted but not opened.

The database is mounted and finally opened.

The database is opened and finally mounted.

No Program Global Area (PGA) is allocated for shared server processes.

User Global Area is stored in System Global Area (SGA).

Shared SQL Area is allocated from Program Global Area (PGA).

Private SQL Area is allocated from Library Cache.

Large Pool is used for SQL work areas.

non-cumulative

multi-version

proactive

stabilizing

cumulative

1. LGWR writes the commit record to disk.

2. LGWR writes all redo entries from Redo Log Buffer to disk.

1. GWR writes only the transaction's redo entries from Redo Log Buffer to disk.

2. LGWR writes the commit record to disk.

1. LGWR puts the commit record to Redo Log Buffer.

2. IGWR writes all redo entries from Redo Log Buffer to disk.

1. LGWR puts the commit record to Redo Log Buffer.

2. If the activity is high, LGWR waits three seconds for other transactions to commit.

3. LGWR writes all redo log entries from Redo Log Buffer to disk.

1. LGWR puts the commit record to Redo Log Buffer.

2. LGWR signals the database writer (DBW) process to write dirty blocks to disk.

3. LGWR writes all redo entries from Redo Log Buffer to disk.

You should check the patch conflict with installed patches before applying the patch.

You should make sure that you have a good backup of the software, database, and configuration files.

You should install the latest O patch before applying the patch.

You should check the fifth digit of the release information to confirm that the Patch Set Update (PSU) is applied successfully.

You should stop all applications running from the software directory that is being patched.

Listeners use only the TCP/IP protocol.

Multiple listener processes can run simultaneously on a host.

Multiple database instances can be registered with a single listener,

Listener-related errors can be traced only at the administrative level.

Only one database instance can be registered with a single listener at any time.

b, c, a

d, a, e

a, e, d, b

d, b, c, a, e

c, b, d, a, e

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE statement with the FINISH keyword

ALTER DATABASE PREPARE TO SWITCHOVER and ALTER DATABASE COMMIT TO SWITCHOVER statements

ALTER DATABASE RECOVER TO STANDBY DATABASE statement with the FINISH keyword

D) ALTER DATABASE PREPARE SWITCHOVER and ALTER DATABASE COMMIT TO SWITCHOVER Statements

615 MB

2.5 GB

4 GB

12 GB

22 GB

It is created for the SALES database in the network domain ACME on the SALESDATA server.

It is created for the SALESDATA database on the SALES server in the network domain called ACME.

It generates an error because the connect identifier name cannot be a part of SERVICE_NAME.

It generates an error because the server configuration mode (dedicated or shared) is not specified.

shut down abort the CDB

shut down abort the PDB

shut down immediate the PDB

shut down immediate the CDB