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

Comment: *

Name: *

Email: *

Verification: *

You upgraded your database from pre-12c to a multitenant container database (CDB) containing pluggable databases (PDBs).
Examine the query and its output:

Which two tasks must you perform to add users with SYSBACKUP, SYSDG, and SYSKM privilege to the password file? (Choose two.)

• A.Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.
• B.Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.
• C.Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE argument set to No.
• D.Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE arguments set to Yes.
• E.Re-create the password file in the Oracle Database 12c format.

Comment: *

Name: *

Email: *

Verification: *

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 local users are unable to use the SET CONTAINER statement.
• C.If fails because the SET CONTAINER statement cannot be used with PDB$SEED as the target pluggable database (PDB).
• D.It fails because common users are unable to use the SET CONTAINER statement.

Comment: *

Name: *

Email: *

Verification: *

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? (Choose three.)

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

Comment: *

Name: *

Email: *

Verification: *

Examine the parameters for your database instance:

Which three statements are true about the process of automatic optimization by using cardinality feedback?
(Choose three.)

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

Comment: *

Name: *

Email: *

Verification: *