[Free] 2019(Nov) EnsurePass Oracle 1z0-062 Dumps with VCE and PDF 31-40

Get Full Version of the Exam
http://www.EnsurePass.com/1z0-062.html

Question No.31

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.

Correct Answer: BE

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 quot;Sharesquot; (resource allocations) to specify how CPU is distributed between PDBs. A CDB Resource Manager Plan also can use quot;utilization limitsquot; 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.

Question No.32

You upgraded your database from pre-12c to a multitenant container database (CDB) containing pluggable databases (PDBs).

Examine the query and its output:

image

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

  1. Assign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.

  2. Grant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.

  3. Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the FORCE argument set to No.

  4. Re-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE arguments set to Yes.

  5. Re-create the password file in the Oracle Database 12c format.

Correct Answer: BD Explanation: orapwd

You can create a database password file using the password file creation utility, ORAPWD. The syntax of the ORAPWD command is as follows:

orapwd FILE=filename [ENTRIES=numusers] [FORCE={y|n}] [ASM={y|n}] [DBUNIQUENAME=dbname] [FORMAT={12|legacy}] [SYSBACKUP={y|n}] [SYSDG={y|n}]

[SYSKM={y|n}] [DELETE={y|n}] [INPUT_FILE=input-fname] force – whether to overwrite existing file (optional),

v$PWFILE_users

12c: V$PWFILE_USERS lists all users in the password file, and indicates whether the user has been granted the SYSDBA, SYSOPER, SYSASM, SYSBACKUP, SYSDG, and SYSKM

privileges.

10c: sts users who have been granted SYSDBA and SYSOPER privileges as derived from the password file.

ColumnDatatypeDescription USERNAMEVARCHAR2(30)

The name of the user that is contained in the password file SYSDBAVARCHAR2(5)

If TRUE, the user can connect with SYSDBA privileges SYSOPERVARCHAR2(5)

If TRUE, the user can connect with SYSOPER privileges Incorrect:

Not E: The format of the v$PWFILE_users file is already in 12c format.

Question No.33

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 gt; REVOKE create table FROM C # # A_ADMIN;

What is the result?

  1. It executes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in root only.

  2. It fails and reports an error because the CONTAINER=ALL clause is not used.

  3. It excludes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in root and all PDBs.

  4. It fails and reports an error because the CONTAINER=CURRENT clause is not used.

  5. It executes successfully and the CREATE TABLE privilege is revoked from C # # A_ADMIN in all PDBs.

Correct Answer: A 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.

Question No.34

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?

  1. The shutdown proceeds immediately. The shutdown proceeds as soon as all transactions in the PDBs are either committed or rolled hack.

  2. The shutdown proceeds as soon as all transactions in the CDB are either committed or rolled back.

  3. The shutdown proceeds as soon as all transactions in both the CDB and PDBs are either committed or rolled back.

  4. The statement results in an error because there are open PDBs.

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

Question No.35

Which action takes place when a file checkpoint occurs?

  1. The checkpoint position is advanced in the checkpoint queue.

  2. All buffers for a checkpointed file that were modified before a specific SCN are written to disk by DBWn and the SCN is stored in the control file.

  3. The Database Writer process (DBWn) writes all dirty buffers in the buffer cache to data files.

  4. The Log Writer process (LGWR) writes all redo entries in the log buffer to online redo log files.

Correct Answer: B

Question No.36

You have installed two 64G flash devices to support the Database Smart Flash Cache feature on your database server that is running on Oracle Linux.

You have set the DB_SMART_FLASH_FILE parameter: DB_FLASH_CACHE_FILE= `/dev/flash_device_1 `,#39; /dev/flash_device_2#39;

How should the DB_FLASH_CACHE_SIZE be configured to use both devices?

  1. Set DB_FLASH_CACHE_ZISE = 64G.

  2. Set DB_FLASH_CACHE_ZISE = 64G, 64G

  3. Set DB_FLASH_CACHE_ZISE = 128G.

  4. DB_FLASH_CACHE_SIZE is automatically configured by the instance at startup.

Correct Answer: B

Explanation:

Smart Flash Cache concept is not new in Oracle 12C – DB Smart Flash Cache in Oracle 11g.

In this release Oracle has made changes related to both initialization parameters used by DB Smart Flash cache. Now you can define many files|devices and its sizes for quot;Database Smart Flash Cachequot; area. In previous releases only one file|device could be defined.

DB_FLASH_CACHE_FILE = /dev/sda, /dev/sdb, /dev/sdc DB_FLASH_CACHE_SIZE = 32G, 32G, 64G

So above settings defines 3 devices which will be in use by quot;DB Smart Flash Cachequot;

/dev/sda – size 32G

/dev/sdb – size 32G

/dev/sdc – size 64G

New view V$FLASHFILESTAT – it#39;s used to determine the cumulative latency and read counts of each file|device and compute the average latency

Question No.37

Which four actions are possible during an Online Data file Move operation? (Choose four.)

  1. Creating and dropping tables in the data file being moved

  2. Performing file shrink of the data file being moved

  3. Querying tables in the data file being moved

  4. Performing Block Media Recovery for a data block in the data file being moved

  5. Flashing back the database

  6. Executing DML statements on objects stored in the data file being moved

Correct Answer: ACEF

Explanation:

You can now move On line Datafile without hove to stop Monoged Recovery and manually copy and rename Files. This can even be used to move Datafiles from or to ASM.

New in Oracle Database 12c: FROM METAUNK. Physical Standby Database is in Active Data Guard Mode (opened READ ONLY and Managed Recovery is running):

It is now possible to online move a Datafile while Managed Recovery is running, ie. the Physical Standby Database is in Active Data Guard Mode. You con use this Command to move the Datafile

A flashback operation does not relocate a moved data file to its previous location. If you move a data file online from one location to another and later flash back the database to a point in time before the move, then the Data file remains in the new location, but the contents of the Data file ore changed to the contents at the time specified in the flashback. Oracle0 Database Administrator#39;s Guide 12c Release 1 (12.1)

Question No.38

You execute the following piece of code with appropriate privileges:

image

User SCOTT has been granted the CREATE SESSION privilege and the MGR role.

Which two statements are true when a session logged in as SCOTT queries the SAL column in the view and the table? (Choose two.)

  1. Data is redacted for the EMP.SAL column only if the SCOTT session does not have the MGR role set.

  2. Data is redacted for EMP.SAL column only if the SCOTT session has the MGR role set.

  3. Data is never redacted for the EMP_V.SAL column.

  4. Data is redacted for the EMP_V.SAL column only if the SCOTT session has the MGR role set.

  5. Data is redacted for the EMP_V.SAL column only if the SCOTT session does not have the MGR role set.

Correct Answer: AC

Explanation:

DBMS_REDACT.FULL completely redacts the column data.

DBMS_REDACT.NONE applies no redaction on the column data. Use this function for development testing purposes. LOB columns are not supported.

The DBMS_REDACT package provides an interface to Oracle Data Redaction, which enables you to mask (redact) data that is returned from queries issued by low-privileged users or an application.

If you create a view chain (that is, a view based on another view), then the Data Redaction policy also applies throughout this view chain. The policies remain in effect all of the way up through this view chain, but if another policy is created for one of these views, then for the columns affected in the subsequent views, this new policy takes precedence.

Question No.39

Identify three scenarios in which you would recommend the use of SQL Performance Analyzer to analyze impact on the performance of SQL statements.

  1. Change in the Oracle Database version

  2. Change in your network infrastructure

  3. Change in the hardware configuration of the database server

  4. Migration of database storage from non-ASM to ASM storage

  5. Database and operating system upgrade

Correct Answer: ACE

Explanation:

Oracle 11g/12c makes further use of SQL tuning sets with the SQL Performance Analyzer, which compares the performance of the statements in a tuning set before and after a database change. The database change can be as major or minor as you like, such as:

(E) Database, operating system, or hardware upgrades.

(A, C) Database, operating system, or hardware configuration changes. Database initialization parameter changes.

Schema changes, such as adding indexes or materialized views. Refreshing optimizer statistics.

Creating or changing SQL profiles.

Question No.40

Your database supports an online transaction processing (OLTP) application. The application is undergoing some major schema changes, such as addition of new indexes and materialized views. You want to check the impact of these changes on workload performance. What should you use to achieve this?

  1. Database replay

  2. SQL Tuning Advisor

  3. SQL Access Advisor

  4. SQL Performance Analyzer

  5. Automatic Workload Repository compare reports

Correct Answer: D

Explanation:

You can use the SQL Performance Analyzer to analyze the SQL performance impact of any type of system change. Examples of common system changes include:

Database upgrades

Configuration changes to the operating system, hardware, or database Database initialization parameter changes

Schema changes, such as adding new indexes or materialized views Gathering optimizer statistics

SQL tuning actions, such as creating SQL profiles

References: http://docs.oracle.com/cd/B28359_01/server.111/b28318/intro.htm#CNCPT961

Get Full Version of the Exam
1z0-062 Dumps
1z0-062 VCE and PDF