Cisco®
Oracle
CompTIA
Checkpoint
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
Salesforce
Amazon
Palo Alto Networks
All Vendors
  2. Home
  3. Exams
  4. Oracle
  5. 1Z0-062

Free Oracle 1Z0-062 Exam Questions (page: 14)

Page 14 of 87
PDF with 419 Questions

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?

  1. CREATE DATABASE LINK HQ USING 'HQ';
  2. CREATE DATABASE LINK HQ CONNECT TO CURRENT_USER USING `HQ';
  3. CREATE PUBLIC DATABASE LINK HQ CONNECT TO scott IDENTIFIED BY tiger USING 'HQ';
  4. CREATE DATABASE LINK HQ CONNECT TO scott IDENTIFIED BY tiger USING 'HQ';

Answer(s): C



To implement Automatic Management (AMM), you set the following parameters:

When you try to start the database instance with these parameter settings, you receive the following error message:
SQL > startup
ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings, see alert log for more information.
Identify the reason the instance failed to start.

  1. The PGA_AGGREGATE_TARGET parameter is set to zero.
  2. The STATISTICS_LEVEL parameter is set to BASIC.
  3. Both the SGA_TARGET and MEMORY_TARGET parameters are set.
  4. The SGA_MAX_SIZE and SGA_TARGET parameter values are not equal.

Answer(s): B

Explanation:

Example:
SQL> startup force
ORA-00824: cannot set SGA_TARGET or MEMORY_TARGET due to existing internal settings
ORA-00848: STATISTICS_LEVEL cannot be set to BASIC with SGA_TARGET or MEMORY_TARGET



Identify two correct statements about multitenant architectures.

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

Answer(s): B,E

Explanation:

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.



You notice a high number of waits for the db file scattered read and db file sequential read events in the recent Automatic Database Diagnostic Monitor (ADDM) report. After further investigation, you find that queries are performing too many full table scans and indexes are not being used even though the filter columns are indexed.
Identify three possible reasons for this.

  1. Missing or stale histogram statistics
  2. Undersized shared pool
  3. High clustering factor for the indexes
  4. High value for the DB_FILE_MULTIBLOCK_READ_COUNT parameter
  5. Oversized buffer cache

Answer(s): A,C,D

Explanation:

D: DB_FILE_MULTIBLOCK_READ_COUNT is one of the parameters you can use to minimize I/O during table scans. It specifies the maximum number of blocks read in one I/O operation during a sequential scan. The total number of I/Os needed to perform a full table scan depends on such factors as the size of the table, the multiblock read count, and whether parallel execution is being utilized for the operation.



Viewing page 14 of 87



Post your Comments and Discuss Oracle 1Z0-062 exam prep with other Community members:

1Z0-062 Exam Discussions & Posts