Oracle 1Z0-062 Online Practice Questions and Exam Preparation

Oracle 1Z0-062 Online Questions & Answers

• Question 131:

  You have successfully taken a database backup by using the command:

  RMAN> BACKUP AS BACKUPSET DATABASE;

  Now you execute this command:

  RMAN> BACKUP INCREMENTAL LEVEL 1 DATABASE;

  What is the outcome?

  A. It fails because an incremental level 1 backup always searches for an image copy as level 0 backup.
  B. It fails because an incremental level 0 backup does not exist.
  C. It takes a backup of blocks that have been formatted since the last full database backup.
  D. It takes an incremental level 0 backup of the database.
  E. It first takes an incremental level 0 backup and then an incremental level 1 backup.
  E. It first takes an incremental level 0 backup and then an incremental level 1 backup.

  ---

  References: https://docs.oracle.com/cd/B19306_01/backup.102/b14192/bkup004.htm (4.4.1.2)

• Question 132:

  You want to create a table, DAILY_ORDERS, for an OLTP application, where data should be compressed during both direct-path INSERT and conventional DML. The table will also be used for queries.

  Which compression option should be used?

  A. ROW STORE COMPRESS
  B. COLUMN STORE COMPRESS FOR QUERY
  C. COLUMN STORE COMPRESS FOR ARCHIVE LOW
  D. ROW STORE COMPRESS ADVANCED
  D. ROW STORE COMPRESS ADVANCED

• Question 133:

  You upgraded from a previous Oracle database version to Oracle Database version to Oracle Database 12c. Your database supports a mixed workload. During the day, lots of insert, update, and delete operations are performed. At night, Extract, Transform, Load (ETL) and batch reporting jobs are run. The ETL jobs perform certain database operations using two or more concurrent sessions.

  After the upgrade, you notice that the performance of ETL jobs has degraded. To ascertain the cause of performance degradation, you want to collect basic statistics such as the level of parallelism, total database time, and the number of I/O requests for the ETL jobs.

  How do you accomplish this?

  A. Examine the Active Session History (ASH) reports for the time period of the ETL or batch reporting runs.
  B. Enable SQL tracing for the queries in the ETL and batch reporting queries and gather diagnostic data from the trace file.
  C. Enable real-time SQL monitoring for ETL jobs and gather diagnostic data from the V$SQL_MONITOR view.
  D. Enable real-time database operation monitoring using the DBMS_SQL_MONITOR.BEGIN_OPERATION function, and then use the DBMS_SQL_MONITOR.REPORT_SQL_MONITOR function to view the required information.
  D. Enable real-time database operation monitoring using the DBMS_SQL_MONITOR.BEGIN_OPERATION function, and then use the DBMS_SQL_MONITOR.REPORT_SQL_MONITOR function to view the required information.

  ---

  * Monitoring database operations Real-Time Database Operations Monitoring enables you to monitor long running database tasks such as batch jobs, scheduler jobs, and Extraction, Transformation, and Loading (ETL) jobs as a composite business operation. This feature tracks the progress of SQL and PL/SQL queries associated with the business operation being monitored. As a DBA or developer, you can define business operations for monitoring by explicitly specifying the start and end of the operation or implicitly with tags that identify the operation.

• Question 134:

  Your database is configured in ARCHIVELOG mode, and a daily full database backup is taken by using RMAN. Control file autobackup is configured.

  Loss of which three database files can lead to an incomplete recovery? (Choose three.)

  A. inactive online redo log file group
  B. a data file belonging to the default temporary tablespace
  C. a data file belonging to the SYSAUX tablespace
  D. server parameter file (SPFILE)
  E. active online redo log file group
  F. all the control flies
  A. inactive online redo log file group
  E. active online redo log file group
  F. all the control flies

• Question 135:

  Examine this configuration for one of your databases:

  1.

  UNDO_RETENTION parameter is 1000

  2.

  retention is not guaranteed

  3.

  The undo tablespace is fixed size Which two statements are true? (Choose two.)

  A. Inactive undo is retained for at least 1000 seconds if free undo space is available.
  B. Active undo never becomes expired.
  C. Active undo is retained for only for 1000 seconds.
  D. Expired undo is retained for 1000 seconds even if transactions fail due to lack of space in the undo tablespace.
  E. Inactive undo is retained for 1000 seconds even if transactions fail due to lack of space in the undo tablespace.
  C. Active undo is retained for only for 1000 seconds.
  E. Inactive undo is retained for 1000 seconds even if transactions fail due to lack of space in the undo tablespace.

  ---

  Reference: https://docs.oracle.com/cd/B19306_01/server.102/b14231/undo.htm

• Question 136:

  You executed the following query:

  

  Considering that all the redo logs are available, what information can you derive from the output of the preceding query?

  A. The time when the last flashback operation in your database was performed
  B. The time when the first flashback operation in our database was performed
  C. The approximate time and the lowest system change number (SCN) to which you can flash back your database
  D. The system change number (SCN) and the time when the Flashback Database was enabled in the database instance
  C. The approximate time and the lowest system change number (SCN) to which you can flash back your database

• Question 137:

  What is a pre-requisite to alter a role?

  A. You should be granted the DBA role.
  B. You should set the OS_ROLES parameter to true.
  C. You should be granted the role with the GRANT OPTION.
  D. You should have the ALTER ANY ROLE system privilege.
  D. You should have the ALTER ANY ROLE system privilege.

• Question 138:

  You administer an online transaction processing (OLTP) system whose database is stored in Automatic Storage Management (ASM) and whose disk group use normal redundancy.

  One of the ASM disks goes offline, and is then dropped because it was not brought online before DISK_REPAIR_TIME elapsed.

  When the disk is replaced and added back to the disk group, the ensuing rebalance operation is too slow.

  Which two recommendations should you make to speed up the rebalance operation if this type of failure happens again? (Choose two.)

  A. Increase the value of the ASM_POWER_LIMIT parameter.
  B. Set the DISK_REPAIR_TIME disk attribute to a lower value.
  C. Specify the statement that adds the disk back to the disk group.
  D. Increase the number of ASMB processes.
  E. Increase the number of DBWR_IO_SLAVES in the ASM instance.
  A. Increase the value of the ASM_POWER_LIMIT parameter.
  D. Increase the number of ASMB processes.

  ---

  A: ASM_POWER_LIMIT specifies the maximum power on an Automatic Storage Management instance for disk rebalancing. The higher the limit, the faster rebalancing will complete. Lower values will take longer, but consume fewer

  processing and I/O resources.

  D:

  *

  Normally a separate process is fired up to do that rebalance. This will take a certain amount of time. If you want it to happen faster, fire up more processes. You tell ASM it can add more processes by increasing the rebalance power.

  *

  ASMB

  ASM Background Process

  Communicates with the ASM instance, managing storage and providing statistics

  Incorrect:

  Not B: A higher, not a lower, value of DISK_REPAIR_TIME would be helpful here.

  Not E: If you implement database writer I/O slaves by setting the DBWR_IO_SLAVES parameter, you configure a single (master) DBWR process that has slave processes that are subservient to it. In addition, I/O slaves can be used to

  "simulate" asynchronous I/O on platforms that do not support asynchronous I/O or implement it inefficiently. Database I/O slaves provide non-blocking, asynchronous requests to simulate asynchronous I/O.

• Question 139:

  Identify two correct statements about multitenant architectures.

  A. Multitenant architecture can be deployed only in a Real Application Clusters (RAC) configuration.
  B. Multiple pluggable databases (PDBs) share certain multitenant container database (CDB) resources.
  C. Multiple CDBs share certain PDB resources.
  D. Multiple non-RAC CDB instances can mount the same PDB as long as they are on the same server.
  E. Patches are always applied at the CDB level.
  F. A PDB can have a private undo tablespace.
  B. Multiple pluggable databases (PDBs) share certain multitenant container database (CDB) resources.
  E. Patches are always applied at the CDB level.

  ---

  B: Using 12c Resource manager you will be able control CPU, Exadata I/O, sessions and parallel servers. A new 12c CDB Resource Manager Plan will use so-called "Shares" (resource allocations) to specify how CPU is distributed between PDBs. A CDB Resource Manager Plan also can use "utilization limits" to limit the CPU usage for a PDB. With a default directive, you do not need to modify the resource plan for each PDB plug and unplug.

  E: New paradigms for rapid patching and upgrades.

  The investment of time and effort to patch one multitenant container database results in patching all of its many pluggable databases. To patch a single pluggable database, you simply unplug/plug to a multitenant container database at a

  different Oracle Database software version.

  Incorrect: Not A:

  *

  The Oracle RAC documentation describes special considerations for a CDB in an Oracle RAC environment.

  *

  Oracle Multitenant is a new option for Oracle Database 12c Enterprise Edition that helps customers reduce IT costs by simplifying consolidation, provisioning, upgrades, and more. It is supported by a new architecture that allows a container database to hold many pluggable databases. And it fully complements other options, including Oracle Real Application Clusters and Oracle Active Data Guard. An existing database can be simply adopted, with no change, as a pluggable database; and no changes are needed in the other tiers of the application. Not D: You can unplug a PDB from one CDB and plug it into a different CDB without altering your schemas or applications. A PDB can be plugged into only one CDB at a time.

  not F:

  *

  UNDO tablespace can NOT be local and stays on the CDB level.

  *

  Redo and undo go hand in hand, and so the CDB as a whole has a single undo tablespace per RAC instance.

• Question 140:

  Which statement is true about the loss of a data file belonging to the default undo tablespace?

  A. The database remains open in read-only mode.
  B. The database is put in MOUNT state and requires recovery to be opened.
  C. The database remains open for querying but no DML statements can be executed except by the users with SYSDBA privilege.
  D. All the noncommitted transactions are lost.
  E. The database instance aborts.
  C. The database remains open for querying but no DML statements can be executed except by the users with SYSDBA privilege.