Lead2Pass: Latest Free Oracle 1Z0-060 Dumps (101-110) Download!

Your multitenant container database (CDB) contains some pluggable databases (PDBs), you execute the following command in the root container:

Which two statements are true?

A.    Schema objects owned by the C# # A_ADMIN common user can be shared across all PDBs.
B.    The C # # A_ADMIN user will be able to use the TEMP_TS temporary tablespace only in root.
C.    The command will, create a common user whose description is contained in the root and each PDB.
D.    The schema for the common user C # # A_ADMIN can be different in each container.
E.    The command will create a user in the root container only because the container clause is not used.

Answer: BE
* Example,Creating Common User in a CDB
This example creates the common user c##testcdb.
CREATE USER c##testcdb IDENTIFIED BY password
A common user’s user name must start with C## or c## and consist only of ASCII characters. The specified tablespace must exist in the root and in all PDBs.
* CREATE USERwith CONTAINER (optional) clause
Creates a common user.
Creates a local user in the current PDB.
*The following rules apply to the current container in a CDB:
The current container can be CDB$ROOT (root) only for common users. The current container can be a particular PDB for both common users and local users.
The current container must be the root when a SQL statement includes CONTAINER = ALL.
You can include the CONTAINER clause in several SQL statements, such as the CREATE USER, ALTER USER, CREATE ROLE, GRANT, REVOKE, and ALTER SYSTEM statements.
Only a common user with the commonly granted SET CONTAINER privilege can run a SQL statement that includes CONTAINER = ALL.

You performed an incremental level 0 backup of a database:
To enable block change tracking after the incremental level 0 backup, you issued this command:
` /mydir/rman_change_track.f’;
To perform an incremental level 1 cumulative backup, you issued this command:
Which three statements are true?

A.    Backup change tracking will sometimes reduce I/O performed during cumulative incremental backups.
B.    The change tracking file must always be backed up when you perform a full database backup.
C.    Block change tracking will always reduce I/O performed during cumulative incremental backups.
D.    More than one database block may be read by an incremental backup for a change made to a single block.
E.    The incremental level 1 backup that immediately follows the enabling of block change tracking will not read
the change tracking file to discover changed blocks.

Answer: BCE
*An incremental level 0 backup backs up all blocks that have ever been in use in this database. *In a cumulative level 1 backup, RMAN backs up all the blocks used since the most recent level 0 incremental backup.
*Oracle Block Change Tracking
Once enabled; this new 10g feature records the modified since last backup and stores the log of it in a block change tracking file using the CTW (Change Tracking Writer) process. During backups RMAN uses the log file to identify the specific blocks that must be backed up. This improves RMAN’s performance as it does not have to scan whole datafiles to detect changed blocks. Logging of changed blocks is performed by the CTRW process which is also responsible for writing data to the block change tracking file.

You find this query being used in your Oracle 12c database:

Which method a used by the optimizer to limit the rows being returned?

A.    A filter is added to the table query dynamically using ROWNUM to limit the rows to 20 percent of the total rows
B.    All the rows are returned to the client or middle tier but only the first 20 percent are returned to the screen
or the application.
C.    A view is created during execution and a filter on the view limits the rows to 20 percent of the total rows.
D.    A TOP-N query is created to limit the rows to 20 percent of the total rows

Answer: C

Which three resources might be prioritized between competing pluggable databases when creating a multitenant container database plan (CDB plan) using Oracle Database Resource Manager?

A.    Maximum Undo per consumer group
B.    Maximum Idle time
C.    Parallel server limit
D.    CPU
E.    Exadata I/O
F.    Local file system I/O

Answer: ACD
Maximum percentage of parallel execution servers that a PDB can use.
Resource utilization limit for CPU.

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: C
*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.

On your Oracle Database, you issue the following commands to create indexes:
SQL > CREATE INDEX oe.ord_customer_ix1 ON or-orders (customer_id, sales_rep_id) INVISIBLE;
SQL> CREATE BITMAP INDEX oe.ord_customer_ix2 ON oe.orders (customer_id, sales_rep_id);
Which two statements are true?

A.    Only the ORD_CUSTOMER_IX1 index created.
B.    Both the indexes are updated when a row is inserted, updated, or deleted in the ORDERS table.
C.    Both the indexes are created: however, only ORD_CUSTOMERS_IX1 is used by the optimizer for
queries on the ORDERS table.
D.    The ORD_CUSTOMER_IX1 index is not used by the optimizer even when the
OPTIMIZER_USE_INVISIBLE_INDEXES parameters is set to true.
E.    Both the indexes are created and used by the optimizer for queries on the ORDERS table.
F.    Both the indexes are created: however, only ORD_CUSTOMERS_IX2 is used by the optimizer for
queries on the ORDERS table.

Answer: BF
Not A: Both indexes are created fine.
B: The invisible index ORD_CUSTOMERS_IX1 and the bitmap index are both updated by DML operations on the Orders table.
F: Since ORD_CUSTOMERS_IX1 is invisible only ORD_CUSTOMERS_IX2 is used by the query optimizer.
Not C,Not D,Not E:
* ord_customer_ix1 is an invisible index and is therefore not used by the optimizer.
* VISIBLE | INVISIBLE Use this clause to specify whether the index is visible or invisible to the optimizer. An invisible index is maintained by DML operations, but it is not be used by the optimizer during queries unless you explicitly set the parameter OPTIMIZER_USE_INVISIBLE_INDEXES to TRUE at the session or system level.
Note: Specify BITMAP to indicate that index is to be created with a bitmap for each distinct key, rather than indexing each row separately. Bitmap indexes store the rowids associated with a key value as a bitmap. Each bit in the bitmap corresponds to a possible rowid. If the bit is set, then it means that the row with the corresponding rowid contains the key value. The internal representation of bitmaps is best suited for applications with low levels of concurrent transactions, such as data warehousing.

Which two statements are true when row archival management is enabled?

A.    The ORA_ARCHIVE_STATE column visibility is controlled by the ROW ARCHIVAL VISIBILITY session
B.    The ORA_ARCHIVE_STATE column is updated manually or by a program that could reference activity
tracking columns, to indicate that a row is no longer considered active.
C.    The ROW ARCHIVAL VISIBILITY session parameter defaults to active rows only.
D.    The ORA_ARCHIVE_STATE column is visible if referenced in the select list of a query.
E.    The ORA_ARCHIVE_STATEcolumn is updated automatically by the Oracle Server based on activity
tracking columns, to Indicate that a row is no longer considered active.

Answer: AB
A:Below we see a case where we set the row archival visibility parameter to “all” there by allowing us to see all of the rows that have been logically deleted:
alter session set row archival visibility = all;
We can then turn-on row invisibility back on by changing row archival visibility = “active”:
alter session set row archival visibility = all;
B:To use ora_archive_state as an alternative to deleting rows, you need the following settings and parameters:
1. Create the table with the row archival clause
create table mytab (col1 number, col2 char(200)) row archival;
2. Now that the table is marked as row archival, you have two methods for removing rows, a permanent solution with the standard delete DML, plus the new syntax where you set ora_archive_state to a non-zero value:
update mytab set ora_archive_state=2 where col2=’FRED’;
3. To make “invisible rows” visible again, you simply set the rows ora_archive_state to zero:
update mytab set ora_archive_state=0 where col2=’FRED’;
* Starting in Oracle 12c, Oracle provides a new feature that allow you to “logically delete” a row in a table without physically removing the row. This effectively makes deleted rows “invisible” to all SQL and DML, but they can be revealed at any time, providing a sort of “instant” rollback method.
To use ora_archive_state as an alternative to deleting rows.

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.

Answer: BCF
*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.

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

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: AE
Unlike unusable indexes, an invisible index is maintained during DML statements.
*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.

If you want to pass the Oracle 12c 1Z0-060 exam sucessfully, recommend to read latest Oracle 12c 1Z0-060 Dumps full version.



Why Choose Lead2pass?

If you want to pass the exam successfully in first attempt you have to choose the best IT study material provider, in my opinion, Lead2pass is one of the best way to prepare for the exam.

Lead2pass Testking Pass4sure Actualtests Others
$99.99 $124.99 $125.99 $189 $29.99-$49.99
Real Questions
Error Correction
Printable PDF
Premium VCE
VCE Simulator
One Time Purchase
Instant Download
Unlimited Install
100% Pass Guarantee
100% Money Back