Testking 1z0 062 pdf Questions are updated and all oracle database 12c installation and administration 1z0 062 pdf answers are verified by experts. Once you have completely prepared with our 1z0 062 pdf exam prep kits you will be ready for the real oracle database 12c installation and administration 1z0 062 pdf exam without a problem. We have Up to date Oracle 1z0 062 pdf dumps study guide. PASSED oracle database 12c installation and administration 1z0 062 pdf First attempt! Here What I Did.

♥♥ 2021 NEW RECOMMEND ♥♥

Free VCE & PDF File for Oracle 1Z0-062 Real Exam (Full Version!)

★ Pass on Your First TRY ★ 100% Money Back Guarantee ★ Realistic Practice Exam Questions

Free Instant Download NEW 1Z0-062 Exam Dumps (PDF & VCE):
Available on: http://www.surepassexam.com/1Z0-062-exam-dumps.html

Q51. Which Oracle Database component is audited by default if the unified Auditing option is enabled? 

A. Oracle Data Pump 

B. Oracle Recovery Manager (RMAN) 

C. Oracle Label Security 

D. Oracle Database Vault 

E. Oracle Real Application Security 


Q52. Examine the query and its output executed In an RDBMS Instance: 

Which three statements are true about the users (other than sys) in the output? 

A. The C # # B_ADMIN user can perform all backup and recovery operations using RMAN only. 

B. The C # # C_ADMIN user can perform the data guard operation with Data Guard Broker. 

C. The C # # A_ADMIN user can perform wallet operations. 

D. The C # # D_ADMIN user can perform backup and recovery operations for Automatic Storage Management (ASM). 

E. The C # # B_ADMIN user can perform all backup and recovery operations using RMAN or SQL* Plus. 

Answer: B,D,E Explanation: 

B: SYSDG administrative privilege has ability to perform Data Guard operations (including startup and shutdown) using Data Guard Broker or dgmgrl. 

D: SYSASM The new (introduced in 11g) SYSASM role to manage the ASM instance, variable extent sizes to reduce shared pool usage, and the ability of an instance to read from a specific disk of a diskgroup 

E (Not A): SYSDBA is like a role in the sense that it is granted, but SYSDBA is a special built-in privilege to allow the DBA full control over the database 


Not C: SYSKM. SYSKM administrative privilege has ability to perform transparent data encryption wallet operations. 


Use the V$PWFILE_USERS view to see the users who have been granted administrative privileges. 

Q53. Examine the resources consumed by a database instance whose current Resource Manager plan is displayed. 

SQL> SELECT name, active_sessions, queue_length, Consumed_cpu_time, cpu_waits, cpu_wait_time 

FROM v$rsrc_consumer_group; 



OLTP__ORDER__ENTRY1029690 467 

OTHES__GROUPS 0 059823664089 


SYS_GROUP 1 02420704 914 




Which two statements are true? 

A. An attempt to start a new session by a user belonging to DSS_QUERIES fails with an error. 

B. An attempt to start a new session by a user belonging to OTHE_GROUPS fails with an error. 

C. The CPU_WAIT_TIME column indicates the total time that sessions in the consumer group waited for the CPU due to resource management. 

D. The CPU_WAIT_TIME column indicates the total time that sessions in the consumer group waited for the CPU due to I/O waits and latch or enqueue contention. 

E. A user belonging to the DSS__QUERIES resource consumer group can create a new session but the session will be queued. 

Answer: C,E 

Q54. Which two are true concerning a multitenant container database with three pluggable database? 

A. All administration tasks must be done to a specific pluggable database. 

B. The pluggable databases increase patching time. 

C. The pluggable databases reduce administration effort. 

D. The pluggable databases are patched together. 

E. Pluggable databases are only used for database consolidation. 

Answer: C,E 

Explanation: The benefits of Oracle Multitenant are brought by implementing a pure deployment choice. The following list calls out the most compelling examples. 

* High consolidation density. (E) The many pluggable databases in a single multitenant 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. This is the same benefit that schema-based consolidation brings. 

* Rapid provisioning and cloning using SQL. 

* New paradigms for rapid patching and upgrades. (D, not B) 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. 

* (C, not A) Manage many databases as one. By consolidating existing databases as pluggable databases, administrators can manage many databases as one. For example, tasks like backup and disaster recovery are performed at the multitenant container database level. 

* Dynamic between pluggable database resource management. In Oracle Database 12c, Resource Manager is extended with specific functionality to control the competition for resources between the pluggable databases within a multitenant container database. Note: 

* 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 multitenant 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. 

Reference: 12c Oracle Multitenant 

Q55. Which three statements are true about Oracle Data Pump export and import operations? 

A. You can detach from a data pump export job and reattach later. 

B. Data pump uses parallel execution server processes to implement parallel import. 

C. Data pump import requires the import file to be in a directory owned by the oracle owner. 

D. The master table is the last object to be exported by the data pump. 

E. You can detach from a data pump import job and reattach later. 

Answer: A,B,D 

Explanation: B: Data Pump can employ multiple worker processes, running in parallel, to increase job performance. 

D: For export jobs, the master table records the location of database objects within a dump file set. / Export builds and maintains the master table for the duration of the job. At the end of an export job, the content of the master table is written to a file in the dump file set. / For import jobs, the master table is loaded from the dump file set and is used to control the sequence of operations for locating objects that need to be imported into the target database. 

Q56. 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. 

Answer: A,B,E 

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. 

Q57. You notice that the elapsed time for an important database scheduler Job is unacceptably long. 

The job belongs to a scheduler job class and window. 

Which two actions would reduce the job's elapsed time? 

A. Increasing the priority of the job class to which the job belongs 

B. Increasing the job's relative priority within the Job class to which it belongs 

C. Increasing the resource allocation for the consumer group mapped to the scheduler job's job class within the plan mapped to the scheduler window 

D. Moving the job to an existing higher priority scheduler window with the same schedule and duration 

E. Increasing the value of the JOB_QUEUE_PROCESSES parameter 

F. Increasing the priority of the scheduler window to which the job belongs 

Answer: B,C 

Explanation: B: Job priorities are used only to prioritize among jobs in the same class. 

Note: Group jobs for prioritization Within the same job class, you can assign priority values of 1-5 to individual jobs so that if two jobs in the class are scheduled to start at the same time, the one with the higher priority takes precedence. This ensures that you do not have a less important job preventing the timely completion of a more important one. 

C: Set resource allocation for member jobs Job classes provide the link between the Database Resource Manager and the Scheduler, because each job class can specify a resource consumer group as an attribute. Member jobs then belong to the specified consumer group and are assigned resources according to settings in the current resource plan. 

Q58. You are administering a database and you receive a requirement to apply the following restrictions: 

1. A connection must be terminated after four unsuccessful login attempts by user. 

2. A user should not be able to create more than four simultaneous sessions. 

3. User session must be terminated after 15 minutes of inactivity. 

4. Users must be prompted to change their passwords every 15 days. 

How would you accomplish these requirements? 

A. by granting a secure application role to the users 

B. by creating and assigning a profile to the users and setting the REMOTE_OS_AUTHENT parameter to FALSE 

C. By creating and assigning a profile to the users and setting the SEC_MAX_FAILED_LOGIN_ATTEMPTS parameter to 4 

D. By Implementing Fine-Grained Auditing (FGA) and setting the REMOTE_LOGIN_PASSWORD_FILE parameter to NONE. 

E. By implementing the database resource Manager plan and setting the SEC_MAX_FAILED_LOGIN_ATTEMPTS parameters to 4. 


Explanation: You can design your applications to automatically grant a role to the user who is trying to log in, provided the user meets criteria that you specify. To do so, you create a secure application role, which is a role that is associated with a PL/SQL procedure (or PL/SQL package that contains multiple procedures). The procedure validates the user: if the user fails the validation, then the user cannot log in. If the user passes the validation, then the procedure grants the user a role so that he or she can use the application. The user has this role only as long as he or she is logged in to the application. When the user logs out, the role is revoked. 


Not B: REMOTE_OS_AUTHENT specifies whether remote clients will be authenticated with the value of the OS_AUTHENT_PREFIX parameter. 

Not C, not E: SEC_MAX_FAILED_LOGIN_ATTEMPTS specifies the number of authentication attempts that can be made by a client on a connection to the server process. 

After the specified number of failure attempts, the connection will be automatically dropped by the server process. 

Not D: REMOTE_LOGIN_PASSWORDFILE specifies whether Oracle checks for a password file. 



One or more databases can use the password file. The password file can contain SYS as well as non-SYS users. 


The password file can be used by only one database. The password file can contain SYS as well as non-SYS users. 


Oracle ignores any password file. Therefore, privileged users must be authenticated by the operating system. 


The REMOTE_OS_AUTHENT parameter is deprecated. It is retained for backward compatibility only. 

Q59. You are connected to a pluggable database (PDB) as a common user with DBA privileges. The STATISTICS_LEVEL parameter is PDB_MODIFIABLE. You execute the following: SQL > ALTER SYSTEM SET STATISTICS_LEVEL = ALL SID = ‘*’ SCOPE = SPFILE; Which is true about the result of this command? 

A. The STATISTICS_LEVEL parameter is set to all whenever this PDB is re-opened. 

B. The STATISTICS_LEVEL parameter is set to ALL whenever any PDB is reopened. 

C. The STATISTICS_LEVEL parameter is set to all whenever the multitenant container database (CDB) is restarted. 

D. Nothing happens; because there is no SPFILE for each PDB, the statement is ignored. 




* In a container architecture, the parameters for PDB will inherit from the root database. That means if statistics_level=all in the root that will cascade to the PDB databases. 

You can over ride this by using Alter system set, if that parameter is pdb modifiable, there is a new column in v$system_parameter for the same. 

Q60. The user SCOTT owns the CUST table that is placed in the SALES tablespace. The user SCOTT opens a session and executes commands as follows: 


1 row created. 


1 row created. 

As a DBA, you execute the following command from another session: 


Which statement is true regarding the effect of this command on the transaction in Scott's session? 

A. The command fails as a transaction is still pending. 

B. The transaction in Scott's session is rolled back and the tablespace becomes readonly. 

C. The command waits and the user SCOTT can execute data manipulation language (DML) statements only as part of the current transaction. 

D. The command hangs until all transactions on the objects in the tablespace commit or rollback, and then the tablespace is placed in readonly mode.