aiotestking uk

1Z0-062 Exam Questions - Online Test


1Z0-062 Premium VCE File

Learn More 100% Pass Guarantee - Dumps Verified - Instant Download
150 Lectures, 20 Hours

Q1. The hr user receiver, the following error while inserting data into the sales table: 

ERROR at line 1: 

ORA-01653; unable to extend table HR.SALES by 128 in tablespace USERS 

On investigation, you find that the users tablespace uses Automnrif Segment Space Management (ASSM). It is the default tablespace for the HR user with an unlimited quota on it. 

Which two methods would you use to resolve this error? 

A. Altering the data life associated with the USERS tablespace to ex automatically 

B. Adding a data life to the USERS tablespace 

C. Changing segment space management for the USERS tablespace to manual 

D. Creating a new tablespace with autoextend enabled and changing the default tablespace of the HR user to the new tablespace 

E. Enabling resumable space allocation by setting the RESUMABLE_TIMEOUT parameter to a nonzero value 

Answer: A,D 

Q2. 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? 

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. 

Answer: A,B,D 

Explanation: 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. 

Reference: Resolving Performance Degradation Over Time 

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

Q4. You created an encrypted tablespace: 

You then closed the encryption wallet because you were advised that this is secure. 

Later in the day, you attempt to create the EMPLOYEES table in the SECURESPACE tablespace with the SALT option on the EMPLOYEE column. 

Which is true about the result? 

A. It creates the table successfully but does not encrypt any inserted data in the EMPNAME column because the wallet must be opened to encrypt columns with SALT. 

B. It generates an error when creating the table because the wallet is closed. 

C. It creates the table successfully, and encrypts any inserted data in the EMPNAME column because the wallet needs to be open only for tablespace creation. 

D. It generates error when creating the table, because the salt option cannot be used with encrypted tablespaces. 

Answer:

Explanation: 

* The environment setup for tablespace encryption is the same as that for transparent data encryption. Before attempting to create an encrypted tablespace, a wallet must be created to hold the encryption key. 

* Setting the tablespace master encryption key is a one-time activity. This creates the master encryption key for tablespace encryption. This key is stored in an external security module (Oracle wallet) and is used to encrypt the tablespace encryption keys. 

* Before you can create an encrypted tablespace, the Oracle wallet containing the tablespace master encryption key must be open. The wallet must also be open before you can access data in an encrypted tablespace. 

* Salt is a way to strengthen the security of encrypted data. It is a random string added to the data before it is encrypted, causing repetition of text in the clear to appear different when encrypted. Salt removes the one common method attackers use to steal data, namely, matching patterns of encrypted text. 

* ALT | NO SALT By default the database appends a random string, called "salt," to the clear text of the column before encrypting it. This default behavior imposes some limitations on encrypted columns: / If you specify SALT during column encryption, then the database does not compress the data in the encrypted column even if you specify table compression for the table. However, the database does compress data in unencrypted columns and encrypted columns without the SALT parameter. 

Q5. Which three statements are true about SQL plan directives? 

A. They are tied to a specific statement or SQL ID. 

B. They instruct the maintenance job to collect missing statistics or perform dynamic sampling to generate a more optimal plan. 

C. They are used to gather only missing statistics. 

D. They are created for a query expression where statistics are missing or the cardinality estimates by the optimizer are incorrect. 

E. They instruct the optimizer to create only column group statistics. 

F. Improve plan accuracy by persisting both compilation and execution statistics in the SYSAUX tablespace. 

Answer: B,D,E 

Explanation: During SQL execution, if a cardinality misestimate occurs, then the database creates SQL plan directives. During SQL compilation, the optimizer examines the query corresponding to the directive to determine whether missing extensions or histograms exist (D). The optimizer records any missing extensions. Subsequent DBMS_STATS calls collect statistics for the extensions. 

The optimizer uses dynamic sampling whenever it does not have sufficient statistics corresponding to the directive. (B, not C) 

E: Currently, the optimizer monitors only column groups. The optimizer does not create an extension on expressions. 

Incorrect: 

Not A: SQL plan directives are not tied to a specific SQL statement or SQL ID. 

Note: 

* A SQL plan directive is additional information and instructions that the optimizer can use to generate a more optimal plan. For example, a SQL plan directive can instruct the optimizer to record a missing extension. 

Q6. What are two benefits of installing Grid Infrastructure software for a stand-alone server before installing and creating an Oracle database? 

A. Effectively implements role separation 

B. Enables you to take advantage of Oracle Managed Files. 

C. Automatically registers the database with Oracle Restart. 

D. Helps you to easily upgrade the database from a prior release. 

E. Enables the Installation of Grid Infrastructure files on block or raw devices. 

Answer: A,C 

Explanation: C: To use Oracle ASM or Oracle Restart, you must first install Oracle Grid Infrastructure for a standalone server before you install and create the database. Otherwise, you must manually register the database with Oracle Restart. 

Desupport of Block and Raw Devices With the release of Oracle Database 11g release 2 (11.2) and Oracle RAC 11g release 2 (11.2), using Database Configuration Assistant or the installer to store Oracle Clusterware or Oracle Database files directly on block or raw devices is not supported. If you intend to upgrade an existing Oracle RAC database, or an Oracle RAC database with Oracle ASM instances, then you can use an existing raw or block device partition, and perform a rolling upgrade of your existing installation. Performing a new installation using block or raw devices is not allowed. 

Reference: Oracle Grid Infrastructure for a Standalone Server, Oracle Database, Installation Guide, 12c 

Q7. You must track all transactions that modify certain tables in the sales schema for at least three years. 

Automatic undo management is enabled for the database with a retention of one day. 

Which two must you do to track the transactions? 

A. Enable supplemental logging for the database. 

B. Specify undo retention guarantee for the database. 

C. Create a Flashback Data Archive in the tablespace where the tables are stored. 

D. Create a Flashback Data Archive in any suitable tablespace. 

E. Enable Flashback Data Archiving for the tables that require tracking. 

Answer: D,E 

Explanation: E: By default, flashback archiving is disabled for any table. You can enable flashback archiving for a table if you have the FLASHBACK ARCHIVE object privilege on the Flashback Data Archive that you want to use for that table. 

D: Creating a Flashback Data Archive 

/ Create a Flashback Data Archive with the CREATE FLASHBACK ARCHIVE statement, specifying the following: 

Name of the Flashback Data Archive 

Name of the first tablespace of the Flashback Data Archive 

(Optional) Maximum amount of space that the Flashback Data Archive can use in the first tablespace 

/ Create a Flashback Data Archive named fla2 that uses tablespace tbs2, whose data will be retained for two years: 

CREATE FLASHBACK ARCHIVE fla2 TABLESPACE tbs2 RETENTION 2 YEAR; 

Q8. Which two statements are true about the use of the procedures listed in the v$sysaux_occupants.move_procedure column? 

A. The procedure may be used for some components to relocate component data to the SYSAUX tablespace from its current tablespace. 

B. The procedure may be used for some components to relocate component data from the SYSAUX tablespace to another tablespace. 

C. All the components may be moved into SYSAUX tablespace. 

D. All the components may be moved from the SYSAUX tablespace. 

Answer: A,B 

Q9. As a user of the ORCL database, you establish a database link to the remote HQ database such that all users in the ORCL database may access tables only from the SCOTT schema in the HQ database. SCOTT’s password is TIGER. The service mane “HQ” is used to connect to the remote HQ database. 

Which command would you execute to create the database link? 

A. CREATE DATABASE LINK HQ USING 'HQ' 

B. CREATE DATABASE LINK HQ CONNECT TO CXJRRENT_USER USING HQ' S 

C. CREATE PUBLIC DATABASE LINK HQ CONNECT TO scott IDENTIFIED BY tiger USING 'HQ' 

D. CREATE DATABASE LINK HQ CONNECT TO scott IDENTIFIED BY tiger USING 'HQ' 

Answer:

Q10. Flashback is enabled for your multitenant container database (CDB), which contains two pluggable database (PDBs). A local user was accidently dropped from one of the PDBs. 

You want to flash back the PDB to the time before the local user was dropped. You connect to the CDB and execute the following commands: 

SQL > SHUTDOWN IMMEDIATE SQL > STARTUP MOUNT SQL > FLASHBACK DATABASE to TIME “TO_DATE (‘08/20/12’ , ‘MM/DD/YY’)”; 

Examine following commands: 

1. ALTER PLUGGABLE DATABASE ALL OPEN; 

2. ALTER DATABASE OPEN; 

3. ALTER DATABASE OPEN RESETLOGS; 

Which command or commands should you execute next to allow updates to the flashback back schema? 

A. Only 1 

B. Only 2 

C. Only 3 

D. 3 and 1 

E. 1 and 2 

Answer:

Explanation: Example (see step23): 

Step 1: 

Run the RMAN FLASHBACK DATABASE command. 

You can specify the target time by using a form of the command shown in the following 

examples: 

FLASHBACK DATABASE TO SCN 46963; 

FLASHBACK DATABASE 

TO RESTORE POINT BEFORE_CHANGES; 

FLASHBACK DATABASE TO TIME 

"TO_DATE('09/20/05','MM/DD/YY')"; 

When the FLASHBACK DATABASE command completes, the database is left mounted and recovered to the specified target time. 

Step 2: 

Make the database available for updates by opening the database with the RESETLOGS option. If the database is currently open read-only, then execute the following commands in SQL*Plus: 

SHUTDOWN IMMEDIATE 

STARTUP MOUNT 

ALTER DATABASE OPEN RESETLOGS;