♥♥ 2018 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
Ucertify offers free demo for 1z0 062 pdf exam. "Oracle Database 12c: Installation and Administration", also known as 1z0 062 pdf exam, is a Oracle Certification. This set of posts, Passing the Oracle 1z0 062 dumps exam, will help you answer those questions. The 1z0 062 pdf Questions & Answers covers all the knowledge points of the real exam. 100% real Oracle oracle database 12c installation and administration 1z0 062 pdf exams and revised by experts!
Q51. In your multitenant container database (CDB) containing pluggable database (PDBs), you granted the CREATE TABLE privilege to the common user C # # A_ADMIN in root and all
PDBs. You execute the following command from the root container:
SQL > REVOKE create table FROM C # # A_ADMIN;
What is the result?
A. It executes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in root only.
B. It fails and reports an error because the CONTAINER=ALL clause is not used.
C. It excludes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in root and all PDBs.
D. It fails and reports an error because the CONTAINER=CURRENT clause is not used.
E. It executes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in all PDBs.
Explanation: REVOKE ..FROM
If the current container is the root:
/ Specify CONTAINER = CURRENT to revoke a locally granted system privilege, object privilege, or role from a common user or common role. The privilege or role is revoked from the user or role only in the root. This clause does not revoke privileges granted with CONTAINER = ALL.
/ Specify CONTAINER = ALL to revoke a commonly granted system privilege, object privilege on a common object, or role from a common user or common role. The privilege or role is revoked from the user or role across the entire CDB. This clause can revoke only a privilege or role granted with CONTAINER = ALL from the specified common user or common role. This clause does not revoke privileges granted locally with CONTAINER = CURRENT. However, any locally granted privileges that depend on the commonly granted privilege being revoked are also revoked.
If you omit this clause, then CONTAINER = CURRENT is the default.
Reference: Oracle Database SQL Language Reference 12c, Revoke
Q52. A warehouse fact table in your Oracle 12c Database is range-partitioned by month and accessed frequently with queries that span multiple partitions
The table has a local prefixed, range partitioned index.
Some of these queries access very few rows in some partitions and all the rows in other partitions, but these queries still perform a full scan for all accessed partitions.
This commonly occurs when the range of dates begins at the end of a month or ends close to the start of a month.
You want an execution plan to be generated that uses indexed access when only a few rows are accessed from a segment, while still allowing full scans for segments where many rows are returned.
Which three methods could transparently help to achieve this result?
A. Using a partial local Index on the warehouse fact table month column with indexing disabled to the table partitions that return most of their rows to the queries.
B. Using a partial local Index on the warehouse fact table month column with indexing disabled for the table partitions that return a few rows to the queries.
C. Using a partitioned view that does a UNION ALL query on the partitions of the warehouse fact table, which retains the existing local partitioned column.
D. Converting the partitioned table to a partitioned view that does a UNION ALL query on the monthly tables, which retains the existing local partitioned column.
E. Using a partial global index on the warehouse fact table month column with indexing disabling for the table partitions that return most of their rows to the queries.
F. Using a partial global index on the warehouse fact table month column with indexing disabled for the table partitions that return a few rows to the queries.
* Oracle 12c now provides the ability to index a subset of partitions and to exclude the others.
Local and global indexes can now be created on a subset of the partitions of a table. Partial Global indexes provide more flexibility in index creation for partitioned tables. For example, index segments can be omitted for the most recent partitions to ensure maximum data ingest rates without impacting the overall data model and access for the partitioned object.
Partial Global Indexes save space and improve performance during loads and queries. This feature supports global indexes that include or index a certain subset of table partitions or subpartitions, and exclude the others. This operation is supported using a default table indexing property. When a table is created or altered, a default indexing property can be specified for the table or its partitions.
Q53. Examine this command:
SQL > exec DBMS_STATS.SET_TABLE_PREFS (‘SH’, ‘CUSTOMERS’, ‘PUBLISH’, ‘false’);
Which three statements are true about the effect of this command?
A. Statistics collection is not done for the CUSTOMERS table when schema stats are gathered.
B. Statistics collection is not done for the CUSTOMERS table when database stats are gathered.
C. Any existing statistics for the CUSTOMERS table are still available to the optimizer at parse time.
D. Statistics gathered on the CUSTOMERS table when schema stats are gathered are stored as pending statistics.
E. Statistics gathered on the CUSTOMERS table when database stats are gathered are stored as pending statistics.
Explanation: * SET_TABLE_PREFS Procedure
This procedure is used to set the statistics preferences of the specified table in the specified schema.
* Example: Using Pending Statistics Assume many modifications have been made to the employees table since the last time statistics were gathered. To ensure that the cost-based optimizer is still picking the best plan, statistics should be gathered once again; however, the user is concerned that new statistics will cause the optimizer to choose bad plans when the current ones are acceptable. The user can do the following:
EXEC DBMS_STATS.SET_TABLE_PREFS('hr', 'employees', 'PUBLISH', 'false');
By setting the employees tables publish preference to FALSE, any statistics gather from now on will not be automatically published. The newly gathered statistics will be marked as pending.
Q54. Which three factors influence the optimizer's choice of an execution plan?
A. the optimizer_mode initialization parameter
B. operating system (OS) statistics
C. cardinality estimates
D. object statistics in the data dictionary
E. fixed baselines
Q55. Which three statements are true about the working of system privileges in a multitenant control database (CDB) that has pluggable databases (PDBs)?
A. System privileges apply only to the PDB in which they are used.
B. Local users cannot use local system privileges on the schema of a common user.
C. The granter of system privileges must possess the set container privilege.
D. Common users connected to a PDB can exercise privileges across other PDBs.
E. System privileges with the with grant option container all clause must be granted to a common user before the common user can grant privileges to other users.
Explanation: A, Not D: In a CDB, PUBLIC is a common role. In a PDB, privileges granted locally to PUBLIC enable all local and common users to exercise these privileges in this
C: A user can only perform common operations on a common role, for example, granting privileges commonly to the role, when the following criteria are met:
The user is a common user whose current container is root.
The user has the SET CONTAINER privilege granted commonly, which means that the
privilege applies in all containers.
The user has privilege controlling the ability to perform the specified operation, and this
privilege has been granted commonly
* Every privilege and role granted to Oracle-supplied users and roles is granted commonly except for system privileges granted to PUBLIC, which are granted locally.
Q56. You plan to implement the distributed database system in your company. You invoke Database Configuration Assistant (DBCA) to create a database on the server. During the installation, DBCA prompts you to specify the Global Database Name.
What must this name be made up of?
A. It must be made up of a database name and a domain name.
B. It must be made up of the value in ORACLE_SID and HOSTNAME.
C. It must be made up of the value that you plan to assign for INSTANCE_NAME and HOSTNAME.
D. It must be made up of the value that you plan to assign for ORACLE_SID and SERVICE_NAMES.
Explanation: Using the DBCA to Create a Database (continued)
3. Database Identification: Enter the Global Database Name in The form database_name.domain_name, and the system identifier (SID). The SID defaults lo the database name and uniquely identifies the instance associated with the database.
4. Management Options: Use this page to set up your database so that it can be managed with Oracle Enterprise Manager. Select the default: "Configure the Database with Enterprise Manager." Optionally, this page allows you to configure alert notifications and daily disk backup area settings.
Note: Yon must configure the listener before you can configure Enterprise Manager (as shown earlier).
Q57. Which three statements are true concerning the multitenant architecture?
A. Each pluggable database (PDB) has its own set of background processes.
B. A PDB can have a private temp tablespace.
C. PDBs can share the sysaux tablespace.
D. Log switches occur only at the multitenant container database (CDB) level.
E. Different PDBs can have different default block sizes.
F. PDBs share a common system tablespace.
G. Instance recovery is always performed at the CDB level.
* A PDB would have its SYSTEM, SYSAUX, TEMP tablespaces.It can also contains other
user created tablespaces in it.
* There is one default temporary tablespace for the entire CDB. However, you can create additional temporary tablespaces in individual PDBs.
* There is a single redo log and a single control file for an entire CDB
* A log switch is the point at which the database stops writing to one redo log file and begins writing to another. Normally, a log switch occurs when the current redo log file is completely filled and writing must continue to the next redo log file.
G: instance recovery The automatic application of redo log records to uncommitted data blocks when an database instance is restarted after a failure.
Incorrect: Not A:
* There is one set of background processes shared by the root and all PDBs. –
* High consolidation density. The many pluggable databases in a single 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.
Not C: There is a separate SYSAUX tablespace for the root and for each PDB.
Not F: There is a separate SYSTEM tablespace for the root and for each PDB. -
Q58. Which two are prerequisites for performing a flashback transaction?
A. Flashback Database must be enabled.
B. Undo retention guarantee for the database must be configured.
C. EXECUTE privilege on the DBMS_FLASHBACK package must be granted to the user flashing back transaction.
D. Supplemental logging must be enabled.
E. Recycle bin must be enabled for the database.
F. Block change tracking must be enabled tor the database.
Reference: Oracle Database Advanced Application Developer's Guide 11g, Using Oracle Flashback Technology
Q59. Which two statements are true about Oracle Managed Files (OMF)?
A. OMF cannot be used in a database that already has data files created with user-specified directions.
B. The file system directions that are specified by OMF parameters are created automatically.
C. OMF can be used with ASM disk groups, as well as with raw devices, for better file management.
D. OMF automatically creates unique file names for table spaces and control files.
E. OMF may affect the location of the redo log files and archived log files.
D: The database internally uses standard file system interfaces to create and delete files as needed for the following database structures:
Tablespaces Redo log files Control files Archived logs Block change tracking files Flashback logs RMAN backups
* Using Oracle-managed files simplifies the administration of an Oracle Database. Oracle-managed files eliminate the need for you, the DBA, to directly manage the operating system files that make up an Oracle Database. With Oracle-managed files, you specify file system directories in which the database automatically creates, names, and manages files at the database object level. For example, you need only specify that you want to create a tablespace; you do not need to specify the name and path of the tablespace's datafile with the DATAFILE clause.
http://www.oracle-base.com/articles/9i/oracle-managed-files.php http://docs.oracle.com/cd/B10500_01/server.920/a96521/omf.htm Reference: What Are Oracle-Managed Files?
Q60. You are administering a database stored in Automatic Storage Management (ASM). You use RMAN to back up the database and the MD_BACKUP command to back up the ASM metadata regularly. You lost an ASM disk group DG1 due to hardware failure.
In which three ways can you re-create the lost disk group and restore the data?
A. Use the MD_RESTORE command to restore metadata for an existing disk group by passing the existing disk group name as an input parameter and use RMAN to restore the data.
B. Use the MKDG command to restore the disk group with the same configuration as the backed-up disk group and data on the disk group.
C. Use the MD_RESTORE command to restore the disk group with the changed disk group specification, failure group specification, name, and other attributes and use RMAN to restore the data.
D. Use the MKDG command to restore the disk group with the same configuration as the backed-up disk group name and same set of disks and failure group configuration, and use RMAN to restore the data.
E. Use the MD_RESTORE command to restore both the metadata and data for the failed disk group.
F. Use the MKDG command to add a new disk group DG1 with the same or different specifications for failure group and other attributes and use RMAN to restore the data.
Explanation: AC (not E):
The md_restore command allows you to restore a disk group from the metadata created by
the md_backup command.
md_restore can’t restore data, only metadata.