You will discover numerous of gains after getting obtained your current Oracle 1Z0-062 accreditation. The 1Z0-062 accreditation is actually a type of ensure which you have very high degree of understanding regarding the The idea team and that you can easily fix a majority of conditions the area of IT encounters. Also, a 1Z0-062 accreditation as well as improving your current price in the eyes of your companies. If you would like for just a job, a 1Z0-062 accreditation will aid you to obtain the very best job. If you would like designed for marketing and advertising, a 1Z0-062 accreditation can certainly make this kind of simple for anyone. Also, a 1Z0-062 accreditation raise your price with your corporation in the process.
2021 Dec 1Z0-062 practice test
Q11. You have altered a non-unique index to be invisible to determine if queries execute within an acceptable response time without using this index.
Which two are possible if table updates are performed which affect the invisible index columns?
A. The index remains invisible.
B. The index is not updated by the DML statements on the indexed table.
C. The index automatically becomes visible in order to have it updated by DML on the table.
D. The index becomes unusable but the table is updated by the DML.
E. The index is updated by the DML on the table.
Answer: A,E
Explanation: Unlike unusable indexes, an invisible index is maintained during DML statements.
Note:
* Oracle 11g allows indexes to be marked as invisible. Invisible indexes are maintained like any other index, but they are ignored by the optimizer unless the OPTIMIZER_USE_INVISIBLE_INDEXES parameter is set to TRUE at the instance or session level. Indexes can be created as invisible by using the INVISIBLE keyword, and their visibility can be toggled using the ALTER INDEX command.
Q12. You conned using SQL Plus to the root container of a multitenant container database (CDB) with SYSDBA privilege.
The CDB has several pluggable databases (PDBs) open in the read/write mode.
There are ongoing transactions in both the CDB and PDBs.
What happens alter issuing the SHUTDOWN TRANSACTIONAL statement?
A. The shutdown proceeds immediately.
The shutdown proceeds as soon as all transactions in the PDBs are either committed or rolled hack.
B. The shutdown proceeds as soon as all transactions in the CDB are either committed or rolled back.
C. The shutdown proceeds as soon as all transactions in both the CDB and PDBs are either committed or rolled back.
D. The statement results in an error because there are open PDBs.
Answer: B
Explanation: * SHUTDOWN [ABORT | IMMEDIATE | NORMAL | TRANSACTIONAL [LOCAL]]
Shuts down a currently running Oracle Database instance, optionally closing and dismounting a database. If the current database is a pluggable database, only the pluggable database is closed. The consolidated instance continues to run.
Shutdown commands that wait for current calls to complete or users to disconnect such as SHUTDOWN NORMAL and SHUTDOWN TRANSACTIONAL have a time limit that the SHUTDOWN command will wait. If all events blocking the shutdown have not occurred within the time limit, the shutdown command cancels with the following message:
ORA-01013: user requested cancel of current operation
* If logged into a CDB, shutdown closes the CDB instance.
To shutdown a CDB or non CDB, you must be connected to the CDB or non CDB instance that you want to close, and then enter
SHUTDOWN
Database closed.
Database dismounted.
Oracle instance shut down.
To shutdown a PDB, you must log into the PDB to issue the SHUTDOWN command.
SHUTDOWN
Pluggable Database closed.
Note:
* Prerequisites for PDB Shutdown
When the current container is a pluggable database (PDB), the SHUTDOWN command can only be used if:
The current user has SYSDBA, SYSOPER, SYSBACKUP, or SYSDG system privilege.
The privilege is either commonly granted or locally granted in the PDB.
The current user exercises the privilege using AS SYSDBA, AS SYSOPER, AS
SYSBACKUP, or AS SYSDG at connect time. To close a PDB, the PDB must be open.
Q13. In your database, you want to ensure that idle sessions that are blocking active are automatically terminated after a specified period of time.
How would you accomplish this?
A. Setting a metric threshold
B. Implementing Database Resource Manager
C. Enabling resumable timeout for user sessions
D. Decreasing the value of the IDLE_TIME resource limit in the default profile
Answer: D
Explanation: An Oracle session is sniped when you set the idle_time parameter to disconnect inactive sessions. (It's only like sniping on ebay in that a time is set for an action to occur.)
Oracle has several ways to disconnect inactive or idle sessions, both from within SQL*Plus via resources profiles (connect_time, idle_time), and with the SQL*net expire time parameter. Here are two ways to disconnect an idle session:
Set the idle_time parameter in the user profile Set the sqlnet.ora parameter expire_time
Q14. Examine the parameters for your database instance:
Which three statements are true about the process of automatic optimization by using cardinality feedback?
A. The optimizer automatically changes a plan during subsequent execution of a SQL statement if there is a huge difference in optimizer estimates and execution statistics.
B. The optimizer can re optimize a query only once using cardinality feedback.
C. The optimizer enables monitoring for cardinality feedback after the first execution of a query.
D. The optimizer does not monitor cardinality feedback if dynamic sampling and multicolumn statistics are enabled.
E. After the optimizer identifies a query as a re-optimization candidate, statistics collected by the collectors are submitted to the optimizer.
Answer: A,C,D
Explanation: C: During the first execution of a SQL statement, an execution plan is generated as usual.
D: if multi-column statistics are not present for the relevant combination of columns, the optimizer can fall back on cardinality feedback.
(not B)* Cardinality feedback. This feature, enabled by default in 11.2, is intended to improve plans for repeated executions.
optimizer_dynamic_sampling optimizer_features_enable
* dynamic sampling or multi-column statistics allow the optimizer to more accurately estimate selectivity of conjunctive predicates.
Note:
* OPTIMIZER_DYNAMIC_SAMPLING controls the level of dynamic sampling performed by the optimizer. Range of values. 0 to 10
* Cardinality feedback was introduced in Oracle Database 11gR2. The purpose of this feature is to automatically improve plans for queries that are executed repeatedly, for which the optimizer does not estimate cardinalities in the plan properly. The optimizer may misestimate cardinalities for a variety of reasons, such as missing or inaccurate statistics, or complex predicates. Whatever the reason for the misestimate, cardinality feedback may be able to help.
Q15. 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.
Answer: B
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.
Leading 1Z0-062 exam engine:
Q16. You use the segment advisor to help determine objects for which space may be reclaimed.
Which three statements are true about the advisor given by the segment advisor?
A. It may advise the use of online table redefinition for tables in dictionary managed tablespace.
B. It may advise the use of segment shrink for tables in dictionary managed tablespaces it the no chained rows.
C. It may advise the use of online table redefinition for tables in locally managed tablespaces
D. It will detect and advise about chained rows.
E. It may advise the use of segment shrink for free list managed tables.
Answer: B,C,D
Explanation: The Segment Advisor generates the following types of advice:
* If the Segment Advisor determines that an object has a significant amount of free space, it recommends online segment shrink. If the object is a table that is not eligible for shrinking, as in the case of a table in a tablespace without automatic segment space management, the Segment Advisor recommends online table redefinition (C).
* (D) If the Segment Advisor encounters a table with row chaining above a certain threshold, it records that fact that the table has an excess of chained rows.
Q17. 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).
Answer: C
Q18. What is the result of executing a TRUNCATE TABLE command on a table that has Flashback Archiving enabled?
A. It fails with the ORA-665610 Invalid DDL statement on history-tracked message
B. The rows in the table are truncated without being archived.
C. The rows in the table are archived, and then truncated.
D. The rows in both the table and the archive are truncated.
Answer: B
Explanation: You cannot roll back a TRUNCATE TABLE statement, nor can you use a FLASHBACK TABLE statement to retrieve the contents of a table that has been truncated.
Q19. 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.
Answer: A,B,D
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
11.1 inclusively.
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.
Note:
* 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.
Q20. A redaction policy was added to the SAL column of the SCOTT.EMP table:
All users have their default set of system privileges.
For which three situations will data not be redacted?
A. SYS sessions, regardless of the roles that are set in the session
B. SYSTEM sessions, regardless of the roles that are set in the session
C. SCOTT sessions, only if the MGR role is set in the session
D. SCOTT sessions, only if the MGR role is granted to SCOTT
E. SCOTT sessions, because he is the owner of the table
F. SYSTEM session, only if the MGR role is set in the session
Answer: A,D,F
Explanation:
* SYS_CONTEXT This is a twist on the SYS_CONTEXT function as it does not use USERENV. With this usage SYS_CONTEXT queries the list of the user's current default roles and returns TRUE if the role is granted.
Example:
SYS_CONTEXT('SYS_SESSION_ROLES', 'SUPERVISOR')
conn scott/tiger@pdborcl
SELECT sys_context('SYS_SESSION_ROLES', 'RESOURCE')
FROM dual;
SYS_CONTEXT('SYS_SESSION_ROLES','SUPERVISOR')
FALSE
conn sys@pdborcl as sysdba
GRANT resource TO scott;
conn scott/tiger@pdborcl SELECT sys_context('SYS_SESSION_ROLES', 'RESOURCE') FROM dual; SYS_CONTEXT('SYS_SESSION_ROLES','SUPERVISOR') TRUE