Oracle 1Z0-062 Online Practice Questions and Exam Preparation

Oracle 1Z0-062 Online Questions & Answers

• Question 91:

  Examine this command.

  

  Now examine these statements:

  

  Which three are true about the result of processing the last statement? (Choose three.)

  A. The parameter is modified in memory and in the parameter file.
  B. The modification persists across instance checkpoint.
  C. The parameter is modified in the parameter file only.
  D. The parameter is modified in memory only.
  E. The modification persists across a SHUTDOWN IMMEDIATE command.
  F. The modification does not persist across a SHUTDOWN TRANSACTIONAL command.
  B. The modification persists across instance checkpoint.
  E. The modification persists across a SHUTDOWN IMMEDIATE command.
  F. The modification does not persist across a SHUTDOWN TRANSACTIONAL command.

• Question 92:

  Which statement is true about redo log files during instance recovery?

  A. All current, online, and archived redo logs are required to complete instance recovery.
  B. All redo log entries in the current and active logs are applied to data files to reconstruct changes made after the most recent checkpoint.
  C. All redo log entries in the current log are applied to data files until the checkpoint position is reached.
  D. All current, active, and inactive redo logs are required to complete instance recovery.
  C. All redo log entries in the current log are applied to data files until the checkpoint position is reached.

  ---

  References: https://docs.oracle.com/cd/A58617_01/server.804/a58396/ch2.htm

• Question 93:

  Which statement is true about the Log Writer process?

  A. It writes when it receives a signal from the checkpoint process (CKPT).
  B. It writes concurrently to all members of multiplexed redo log groups.
  C. It writes after the Database Writer process writes dirty buffers to disk.
  D. It writes when a user commits a transaction.
  D. It writes when a user commits a transaction.

  ---

  References:

  http://docs.oracle.com/cd/B19306_01/server.102/b14220/process.htm (see log writer process (LGWR))

• Question 94:

  Examine the structure of the sales table, which is stored in a locally managed tablespace with Automatic Segment Space Management (ASSM) enabled.

  

  You want to perform online segment shrink to reclaim fragmented free space below the high water mark. What should you ensure before the start of the operation?

  A. Row movement is enabled.
  B. Referential integrity constraints for the table are disabled.
  C. No queries are running on this table.
  D. Extra disk space equivalent to the size of the segment is available in the tablespace.
  E. No pending transaction exists on the table.
  A. Row movement is enabled.

• Question 95:

  You run a script that completes successfully using SQL*Plus that performs these actions:

  1.

  Creates a multitenant container database (CDB)

  2.

  Plugs in three pluggable databases (PDBs)

  3.

  Shuts down the CDB instance

  4.

  Starts up the CDB instance using STARTUP OPEN READ WRITE

  Which two statements are true about the outcome after running the script? (Choose two.)

  A. The seed will be in mount state.
  B. The seed will be opened read-only.
  C. The seed will be opened read/write.
  D. The other PDBs will be in mount state.
  E. The other PDBs will be opened read-only.
  F. The PDBs will be opened read/write.
  B. The seed will be opened read-only.
  D. The other PDBs will be in mount state.

  ---

  B: The seed is always read-only.

  D: Pluggable databases can be started and stopped using SQL*Plus commands or the ALTER PLUGGABLE DATABASE command.

• Question 96:

  Which three statements are true concerning the multitenant architecture? (Choose three.)

  A. Each pluggable database (PDB) has its own set of background processes.
  B. A PDB can have a private temp tablespace.
  C. PDBs can share the sysaux tablespace.
  D. Log switches occur only at the multitenant container database (CDB) level.
  E. Different PDBs can have different default block sizes.
  F. PDBs share a common system tablespace.
  G. Instance recovery is always performed at the CDB level.
  B. A PDB can have a private temp tablespace.
  D. Log switches occur only at the multitenant container database (CDB) level.
  G. Instance recovery is always performed at the CDB level.

  ---

  B:

  *

  A PDB would have its SYSTEM, SYSAUX, TEMP tablespaces. It can also contain other user created tablespaces in it.

  *

  There is one default temporary tablespace for the entire CDB. However, you can create additional temporary tablespaces in individual PDBs.

  D:

  *

  There is a single redo log and a single control file for an entire CDB

  *

  A log switch is the point at which the database stops writing to one redo log file and begins writing to another. Normally, a log switch occurs when the current redo log file is completely filled and writing must continue to the next redo log file.

  G: instance recovery

  The automatic application of redo log records to uncommitted data blocks when a database instance is restarted after a failure.

  Incorrect: Not A:

  *

  There is one set of background processes shared by the root and all PDBs.

  *

  High consolidation density. The many pluggable databases in a single container database share its memory and background processes, letting you operate many more pluggable databases on a particular platform than you can single databases that use the old architecture.

  Not C: There is a separate SYSAUX tablespace for the root and for each PDB.

  Not F: There is a separate SYSTEM tablespace for the root and for each PDB.

• Question 97:

  You notice a performance change in your production Oracle database and you want to know which change has made this performance difference. You generate the Compare Period Automatic Database Diagnostic Monitor (ADDM) report to further investigation.

  Which three findings would you get from the report? (Choose three.)

  A. It detects any configuration change that caused a performance difference in both time periods.
  B. It identifies any workload change that caused a performance difference in both time periods.
  C. It detects the top wait events causing performance degradation.
  D. It shows the resource usage for CPU, memory, and I/O in both time periods.
  E. It shows the difference in the size of memory pools in both time periods.
  F. It gives information about statistics collection in both time periods.
  A. It detects any configuration change that caused a performance difference in both time periods.
  B. It identifies any workload change that caused a performance difference in both time periods.
  D. It shows the resource usage for CPU, memory, and I/O in both time periods.

  ---

  Keyword: shows the difference.

  *

  Full ADDM analysis across two AWR snapshot periods Detects causes, measure effects, then correlates them Causes: workload changes, configuration changes Effects: regressed SQL, reach resource limits (CPU, I/O, memory, interconnect) Makes actionable recommendations along with quantified impact

  *

  Identify what changed / Configuration changes, workload changes

  *

  Performance degradation of the database occurs when your database was performing optimally in the past, such as 6 months ago, but has gradually degraded to a point where it becomes noticeable to the users. The Automatic Workload Repository (AWR) Compare Periods report enables you to compare database performance between two periods of time.

  While an AWR report shows AWR data between two snapshots (or two points in time), the AWR Compare Periods report shows the difference (ABE) between two periods (or two AWR reports with a total of four snapshots). Using the AWR Compare Periods report helps you to identify detailed performance attributes and configuration settings that differ between two time periods.

• Question 98:

  Identify three scenarios in which you would recommend the use of SQL Performance Analyzer to analyze impact on the performance of SQL statements.

  A. Change in the Oracle Database version
  B. Change in your network infrastructure
  C. Change in the hardware configuration of the database server
  D. Migration of database storage from non-ASM to ASM storage
  E. Database and operating system upgrade
  A. Change in the Oracle Database version
  C. Change in the hardware configuration of the database server
  E. Database and operating system upgrade

  ---

  Oracle 11g/12c makes further use of SQL tuning sets with the SQL Performance Analyzer, which compares the performance of the statements in a tuning set before and after a database change. The database change can be as major or minor as you like, such as:

  *

  (E) Database, operating system, or hardware upgrades.

  *

  (A,C) Database, operating system, or hardware configuration changes.

  *

  Database initialization parameter changes.

  *

  Schema changes, such as adding indexes or materialized views.

  *

  Refreshing optimizer statistics.

  *

  Creating or changing SQL profiles.

• Question 99:

  Identify the persistent configuration setting for the target database that can be set for the backup by using RMAN. (Choose all that apply.)

  A. Backup retention policy
  B. Default backup device type
  C. Default destinations for backups
  D. Multiple backup device types for single backup
  E. Default section size for backups
  A. Backup retention policy
  B. Default backup device type
  C. Default destinations for backups

  ---

  http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfb.htm#BRADV89399

• Question 100:

  Which three statements are true about windows? (Choose three.)

  A. Only one window can be open at any given time
  B. Consumer groups are associated with windows
  C. Windows work with job classes to control resource allocation
  D. The database service name must be provided during windows creation
  E. Windows can automatically start job or change resource allocation among jobs for various time periods
  A. Only one window can be open at any given time
  C. Windows work with job classes to control resource allocation
  E. Windows can automatically start job or change resource allocation among jobs for various time periods