Exact of 1Z0-062 free exam materials and preparation labs for Oracle certification for examinee, Real Success Guaranteed with Updated 1Z0-062 pdf dumps vce Materials. 100% PASS Oracle Database 12c: Installation and Administration exam Today!
2016 Jun 1Z0-062 Study Guide Questions:
Q101. What is the effect of specifying the "ENABLE PLUGGABLE DATABASE" clause in a "CREATE DATABASE” statement?
A. It will create a multitenant container database (CDB) with only the root opened.
B. It will create a CDB with root opened and seed read only.
C. It will create a CDB with root and seed opened and one PDB mounted.
D. It will create a CDB that must be plugged into an existing CDB.
E. It will create a CDB with root opened and seed mounted.
Explanation: * The CREATE DATABASE ... ENABLE PLUGGABLE DATABASE SQL statement creates a new CDB. If you do not specify the ENABLE PLUGGABLE DATABASE clause, then the newly created database is a non-CDB and can never contain PDBs.
Along with the root (CDB$ROOT), Oracle Database automatically creates a seed PDB (PDB$SEED). The following graphic shows a newly created CDB:
Description of admin095.png follows
* Creating a PDB Rather than constructing the data dictionary tables that define an empty PDB from scratch, and then populating its Obj$ and Dependency$ tables, the empty PDB is created when the CDB is created. (Here, we use empty to mean containing no customer-created artifacts.) It is referred to as the seed PDB and has the name PDB$Seed. Every CDB non-negotiably contains a seed PDB; it is non-negotiably always open in read-only mode. This has no conceptual significance; rather, it is just an optimization device. The create PDB operation is implemented as a special case of the clone PDB operation.
Q102. You wish to enable an audit policy for all database users, except SYS, SYSTEM, and SCOTT.
You issue the following statements:
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SYS;
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SYSTEM;
SQL> AUDIT POLICY ORA_DATABASE_PARAMETER EXCEPT SCOTT;
For which database users is the audit policy now active?
A. All users except SYS
B. All users except SCOTT
C. All users except sys and SCOTT
D. All users except sys, system, and SCOTT
Explanation: If you run multiple AUDIT statements on the same unified audit policy but specify different EXCEPT users, then Oracle Database uses the last exception user list, not any of the users from the preceding lists. This means the effect of the earlier AUDIT POLICY ... EXCEPT statements are overridden by the latest AUDIT POLICY ... EXCEPT statement.
* The ORA_DATABASE_PARAMETER policy audits commonly used Oracle Database parameter settings. By default, this policy is not enabled.
* You can use the keyword ALL to audit all actions. The following example shows how to audit all actions on the HR.EMPLOYEES table, except actions by user pmulligan.
Example Auditing All Actions on a Table
CREATE AUDIT POLICY all_actions_on_hr_emp_pol ACTIONS ALL ON HR.EMPLOYEES;
AUDIT POLICY all_actions_on_hr_emp_pol EXCEPT pmulligan;
Reference: Oracle Database Security Guide 12c, About Enabling Unified Audit Policies
Q103. 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.
Reference: http://docs.oracle.com/cd/B19306_01/server.102/b14220/process.htm (see log writer process (LGWR))
Up to date 1z0-062 ebook:
Q104. In your multitenant container database (CDB) with two pluggable database (PDBs). You want to create a new PDB by using SQL Developer.
Which statement is true?
A. The CDB must be open.
B. The CDB must be in the mount stage.
C. The CDB must be in the nomount stage.
D. Alt existing PDBs must be closed.
* Creating a PDB Rather than constructing the data dictionary tables that define an empty PDB from scratch, and then populating its Obj$ and Dependency$ tables, the empty PDB is created when the CDB is created. (Here, we use empty to mean containing no customer-created artifacts.) It is referred to as the seed PDB and has the name PDB$Seed. Every CDB non-negotiably contains a seed PDB; it is non-negotiably always open in read-only mode. This has no conceptual significance; rather, it is just an optimization device. The create PDB operation is implemented as a special case of the clone PDB operation. The size of the seed PDB is only about 1 gigabyte and it takes only a few seconds on a typical machine to copy it.
Q105. You plan to create a database by using the Database Configuration Assistant (DBCA), with the following specifications:
Applications will connect to the database via a middle tier.
The number of concurrent user connections will be high.
The database will have mixed workload, with the execution of complex BI queries scheduled at night.
Which DBCA option must you choose to create the database?
A. a General Purpose database template with default memory allocation
B. a Data Warehouse database template, with the dedicated server mode option and AMM enabled
C. a General Purpose database template, with the shared server mode option and Automatic Memory Management (AMM) enabled
D. a default database configuration
Q106. You want to flash back a test database by five hours.
You issue this command:
SQL > FLASHBACK DATABASE TO TIMESTAMP (SYSDATE - 5/24);
Which two statements are true about this flashback scenario?
A. The database must have multiplexed redo logs for the flashback to succeed.
B. The database must be MOUNTED for the flashback to succeed.
C. The database must use block change tracking for the flashback to succeed.
D. The database must be opened in restricted mode for the flashback to succeed.
E. The database must be opened with the RESETLOGS option after the flashback is complete.
F. The database must be opened in read-only mode to check if the database has been flashed back to the correct SCN.
Vivid 1z0-062 ebook:
Q107. Which three statements are true about Flashback Database?
A. Flashback logs are written sequentially, and are archived.
B. Flashback Database uses a restored control file to recover a database.
C. The Oracle database automatically creates, deletes, and resides flashback logs in the Fast Recovery Area.
D. Flashback Database can recover a database to the state that it was in before a reset logs operation.
E. Flashback Database can recover a data file that was dropped during the span of time of the flashback.
F. Flashback logs are used to restore to the blocks' before images, and then the redo data may be used to roll forward to the desired flashback time.
Explanation: * Flashback Database uses its own logging mechanism, creating flashback logs and storing them in the fast recovery area (C). You can only use Flashback Database if flashback logs are available. To take advantage of this feature, you must set up your database in advance to create flashback logs.
* To enable Flashback Database, you configure a fast recovery area and set a flashback retention target. This retention target specifies how far back you can rewind a database with Flashback Database.
From that time onwards, at regular intervals, the database copies images of each altered block in every data file into the flashback logs. These block images can later be reused to reconstruct the data file contents for any moment at which logs were captured. (F)
Incorrect: Not E: You cannot use Flashback Database alone to retrieve a dropped data file. If you flash back a database to a time when a dropped data file existed in the database, only the data file entry is added to the control file. You can only recover the dropped data file by using RMAN to fully restore and recover the data file.
Reference: Oracle Database Backup and Recovery User's Guide 12c R
Q108. You support Oracle Database 12c Oracle Database 11g, and Oracle Database log on the same server.
All databases of all versions use Automatic Storage Management (ASM).
Which three statements are true about the ASM disk group compatibility attributes that are set for a disk group?
A. The ASM compatibility attribute controls the format of the disk group metadata.
B. RDBMS compatibility together with the database version determines whether a database Instance can mount the ASM disk group.
C. The RDBMS compatibility setting allows only databases set to the same version as the compatibility value, to mount the ASM disk group.
D. The ASM compatibility attribute determines some of the ASM features that may be used by the Oracle disk group.
E. The ADVM compatibility attribute determines the ACFS features that may be used by the Oracle 10 g database.
Explanation: AD: The value for the disk group COMPATIBLE.ASM attribute determines the minimum software version for an Oracle ASM instance that can use the disk group. This setting also affects the format of the data structures for the Oracle ASM metadata on the disk.
B: The value for the disk group COMPATIBLE.RDBMS attribute determines the minimum COMPATIBLE database initialization parameter setting for any database instance that is allowed to use the disk group. Before advancing the COMPATIBLE.RDBMS attribute, ensure that the values for the COMPATIBLE initialization parameter for all of the databases that access the disk group are set to at least the value of the new setting for COMPATIBLE.RDBMS.
For example, if the COMPATIBLE initialization parameters of the databases are set to either 11.1 or 11.2, then COMPATIBLE.RDBMS can be set to any value between 10.1 and
Not E: /The value for the disk group COMPATIBLE.ADVM attribute determines whether the disk group can contain Oracle ASM volumes. The value must be set to 11.2 or higher. Before setting this attribute, the COMPATIBLE.ASM value must be 11.2 or higher. Also, the Oracle ADVM volume drivers must be loaded in the supported environment.
/ You can create an Oracle ASM Dynamic Volume Manager (Oracle ADVM) volume in a disk group. The volume device associated with the dynamic volume can then be used to host an Oracle ACFS file system.
The compatibility parameters COMPATIBLE.ASM and COMPATIBLE.ADVM must be set to
11.2 or higher for the disk group.
* The disk group attributes that determine compatibility are COMPATIBLE.ASM, COMPATIBLE.RDBMS. and COMPATIBLE.ADVM. The COMPATIBLE.ASM and COMPATIBLE.RDBMS attribute settings determine the minimum Oracle Database software version numbers that a system can use for Oracle ASM and the database instance types respectively. For example, if the Oracle ASM compatibility setting is 11.2, and RDBMS compatibility is set to 11.1, then the Oracle ASM software version must be at least 11.2, and the Oracle Database client software version must be at least 11.1. The COMPATIBLE.ADVM attribute determines whether the Oracle ASM Dynamic Volume Manager feature can create an volume in a disk group.
Q109. 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.
Q110. You are connected using SQL* Plus to a multitenant container database (CDB) with SYSDBA privileges and execute the following sequence statements:
What is the result of the last SET CONTAINER statement and why is it so?
A. It succeeds because the PDB_ADMIN user has the required privileges.
B. It fails because common users are unable to use the SET CONTAINER statement.
C. It fails because local users are unable to use the SET CONTAINER statement.
D. If fails because the SET CONTAINER statement cannot be used with PDB$SEED as the target pluggable database (PDB).