★ Pass on Your First TRY ★ 100% Money Back Guarantee ★ Realistic Practice Exam Questions
Exam Code: 1Z0-062 (Practice Exam Latest Test Questions VCE PDF)
Exam Name: Oracle Database 12c: Installation and Administration
Certification Provider: Oracle
Free Today! Guaranteed Training- Pass 1Z0-062 Exam.
2016 Jun 1Z0-062 Study Guide Questions:
Q81. Examine the parameter for your database instance:
You generated the execution plan for the following query in the plan table and noticed that the nested loop join was done. After actual execution of the query, you notice that the hash join was done in the execution plan:
Identify the reason why the optimizer chose different execution plans.
A. The optimizer used a dynamic plan for the query.
B. The optimizer chose different plans because automatic dynamic sampling was enabled.
C. The optimizer used re-optimization cardinality feedback for the query.
D. The optimizer chose different plan because extended statistics were created for the columns used.
Explanation: * optimizer_dynamic_sampling OPTIMIZER_DYNAMIC_SAMPLING controls both when the database gathers dynamic statistics, and the size of the sample that the optimizer uses to gather the statistics. Range of values0 to 11
Q82. Which statement is true concerning dropping a pluggable database (PDB)?
A. The PDB must be open in read-only mode.
B. The PDB must be in mount state.
C. The PDB must be unplugged.
D. The PDB data files are always removed from disk.
E. A dropped PDB can never be plugged back into a multitenant container database (CDB).
Q83. Which two statements are true about extents?
A. Blocks belonging to an extent can be spread across multiple data files.
B. Data blocks in an extent are logically contiguous but can be non-contiguous on disk.
C. The blocks of a newly allocated extent, although free, may have been used before.
D. Data blocks in an extent are automatically reclaimed for use by other objects in a tablespaee when all the rows in a table are deleted.
Up to the minute 1z0-062 dumps:
Q84. Your multitenant container database has three pluggable databases (PDBs): PDB1, PDB2, and PDB3.
Which two RMAN commands may be; used to back up only the PDB1 pluggable database?
A. BACKUP PLUGGABLE DATABASE PDB1 while connected to the root container
B. BACKUP PLUGGABLE DATABASE PDB1 while connected to the PDB1 container
C. BACKUP DATABASE while connected to the PDB1 container
D. BACKUP DATABASE while connected to the boot container
E. BACKUP PLUGGABLE database PDB1 while connected to PDB2
Explanation: To perform operations on a single PDB, you can connect as target either to the root or directly to the PDB.
* (A) If you connect to the root, you must use the PLUGGABLE DATABASE syntax in your RMAN commands. For example, to back up a PDB, you use the BACKUP PLUGGABLE DATABASE command.
* (C)If instead you connect directly to a PDB, you can use the same commands that you would use when connecting to a non-CDB. For example, to back up a PDB, you would use the BACKUP DATABASE command.
Reference: Oracle Database Backup and Recovery User's Guide 12c, About Backup and Recovery of CDBs
Q85. You notice a performance change in your production Oracle 12c database. You want to know which change caused this performance difference.
Which method or feature should you use?
A. Compare Period ADDM report
B. AWR Compare Period report
C. Active Session History (ASH) report
D. Taking a new snapshot and comparing it with a preserved snapshot
Explanation: The awrddrpt.sql report is the Automated Workload Repository Compare
Period Report. The awrddrpt.sql script is located in the $ORACLE_HOME/rdbms/admin directory.
Not A: Compare Period ADDM
Use this report to perform a high-level comparison of one workload replay to its capture or to another replay of the same capture. Only workload replays that contain at least 5 minutes of database time can be compared using this report.
Q86. Which three statements are true about using flashback database in a multitenant container database (CDB)?
A. The root container can be flashed back without flashing back the pluggable databases (PDBs).
B. To enable flashback database, the CDB must be mounted.
C. Individual PDBs can be flashed back without flashing back the entire CDB.
D. The DB_FLASHBACK RETENTION_TARGET parameter must be set to enable flashback of the CDB.
E. A CDB can be flashed back specifying the desired target point in time or an SCN, but not a restore point.
Real 1z0-062 ebook:
Q87. Which two statements are true when row archival management is enabled?
A. The ORA_ARCHIVE_STATE column visibility is controlled by the ROW ARCHIVAL VISIBILITY session parameter.
B. The ORA_ARCHIVE_STATE column is updated manually or by a program that could reference activity tracking columns, to indicate that a row is no longer considered active.
C. The ROW ARCHIVAL VISIBILITY session parameter defaults to active rows only.
D. The ORA_ARCHIVE_STATE column is visible if referenced in the select list of a query.
E. The ORA_ARCHIVE_STATE column is updated automatically by the Oracle Server based on activity tracking columns, to Indicate that a row is no longer considered active.
Explanation: A: Below we see a case where we set the row archival visibility parameter to "all" thereby allowing us to see all of the rows that have been logically deleted:
alter session set row archival visibility = all;
We can then turn-on row invisibility back on by changing row archival visibility = "active": alter session set row archival visibility = all;
B: To use ora_archive_state as an alternative to deleting rows, you need the following settings and parameters:
1. Create the table with the row archival clause
create table mytab (col1 number, col2 char(200)) row archival;
2. Now that the table is marked as row archival, you have two methods for removing rows, a permanent solution with the standard delete DML, plus the new syntax where you set ora_archive_state to a non-zero value:
update mytab set ora_archive_state=2 where col2='FRED'
3. To make "invisible rows" visible again, you simply set the rows ora_archive_state to zero:
update mytab set ora_archive_state=0 where col2='FRED' Note:
* Starting in Oracle 12c, Oracle provides a new feature that allow you to "logically delete" a row in a table without physically removing the row. This effectively makes deleted rows "invisible" to all SQL and DML, but they can be revealed at any time, providing a sort of "instant" rollback method.
To use ora_archive_state as an alternative to deleting rows.
Q88. Identify three benefits of Unified Auditing.
A. Decreased use of storage to store audit trail rows in the database.
B. It improves overall auditing performance.
C. It guarantees zero-loss auditing.
D. The audit trail cannot be easily modified because it is read-only.
E. It automatically audits Recovery Manager (RMAN) events.
Explanation: A: Starting with 12c, Oracle has unified all of the auditing types into one single unit called Unified auditing. You don’t have to turn on or off all of the different auidting types individually and as a matter of fact auditing is enabled by default right out of the box. The AUD$ and FGA$ tables have been replaced with one single audit trail table. All of the audit data is now stored in Secure Files table thus improving the overall management aspects of audit data itself.
B: Further the audit data can also be buffered solving most of the common performance related problems seen on busy environments.
E: Unified Auditing is able to collect audit data for Fine Grained Audit, RMAN, Data Pump, Label Security, Database Vault and Real Application Security operations.
* Benefits of the Unified Audit Trail
The benefits of a unified audit trail are many: / (B) Overall auditing performance is greatly improved. The default mode that unified audit works is Queued Write mode. In this mode, the audit records are batched in SGA queue and is persisted in a periodic way. Because the audit records are written to SGA queue, there is a significant performance improvement.
/ The unified auditing functionality is always enabled and does not depend on the initialization parameters that were used in previous releases
/ (A) The audit records, including records from the SYS audit trail, for all the audited components of your Oracle Database installation are placed in one location and in one format, rather than your having to look in different places to find audit trails in varying formats. This consolidated view enables auditors to co-relate audit information from different components. For example, if an error occurred during an INSERT statement, standard auditing can indicate the error number and the SQL that was executed. Oracle Database Vault-specific information can indicate whether this error happened because of a command rule violation or realm violation. Note that there will be two audit records with a distinct AUDIT_TYPE. With this unification in place, SYS audit records appear with AUDIT_TYPE set to Standard Audit.
/ The management and security of the audit trail is also improved by having it in single audit trail.
/ You can create named audit policies that enable you to audit the supported components listed at the beginning of this section, as well as SYS administrative users. Furthermore, you can build conditions and exclusions into your policies.
* Oracle Database 12c Unified Auditing enables selective and effective auditing inside the Oracle database using policies and conditions. The new policy based syntax simplifies management of auditing within the database and provides the ability to accelerate auditing based on conditions.
* The new architecture unifies the existing audit trails into a single audit trail, enabling simplified management and increasing the security of audit data generated by the database.
Q89. Examine the commands executed to monitor database operations:
$> conn sys oracle/oracle@prod as sysdba
SQL > VAR eid NUMBER
SQL > EXEC: eid := DBMS_SQL_MONITOR.BEGIN_OPERATION (‘batch_job’ , FORCED_TRACKING => ‘Y’);
Which two statements are true?
A. Database operations will be monitored only when they consume a significant amount of resource.
B. Database operations for all sessions will be monitored.
C. Database operations will be monitored only if the STATISTICS_LEVEL parameter is set to TYPICAL and CONTROL_MANAGEMENT_PACK_ACCESS is set DIAGNISTIC + TUNING.
D. Only DML and DDL statements will be monitored for the session.
E. All subsequent statements in the session will be treated as one database operation and will be monitored.
Explanation: C: Setting the CONTROL_MANAGEMENT_PACK_ACCESS initialization parameter to DIAGNOSTIC+TUNING (default) enables monitoring of database operations. Real-Time SQL Monitoring is a feature of the Oracle Database Tuning Pack.
* The DBMS_SQL_MONITOR package provides information about Real-time SQL
Monitoring and Real-time Database Operation Monitoring.
*(not B) BEGIN_OPERATION Function
starts a composite database operation in the current session.
/ (E) FORCE_TRACKING - forces the composite database operation to be tracked when the operation starts. You can also use the string variable 'Y'.
/ (not A) NO_FORCE_TRACKING - the operation will be tracked only when it has consumed at least 5 seconds of CPU or I/O time. You can also use the string variable 'N'.
Q90. Your database is open and the listener LISTNENER is up. You issue the command:
What is the effect of reload on sessions that were originally established by listener?
A. Only sessions based on static listener registrations are disconnected.
B. Existing connections are not disconnected; however, they cannot perform any operations until the listener completes the re-registration of the database instance and service handlers.
C. The sessions are not affected and continue to function normally.
D. All the sessions are terminated and active transactions are rolled back.
see more Oracle Database 12c: Installation and Administration