NEW QUESTION NO: 5
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.
Answer: A,C,E
Explanation/Reference:
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 PDB only.
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
Note:
* 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.

NEW QUESTION NO: 6
Which three statements are true concerning the multitenant architecture? (Choose three.)
A. Each pluggable database (PDB) has its own set of background processes.
B. A PDB can have a private TEMPtablespace.
C. PDBs can share the SYSAUXtablespace.
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.
Answer: B,D,G
Explanation/Reference:
Explanation:
B:
* 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.
D:
* 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 Answers:
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.
C: There is a separate SYSAUX tablespace for the root and for each PDB.
F: There is a separate SYSTEM tablespace for the root and for each PDB. -

NEW QUESTION NO: 7
The tnsnames.ora file has an entry for the service alias ORCL as follows:

The TNSPING command executes successfully when tested with ORCL; however, from the same OS user session, you are not able to connect to the database instance with the following command:
SQL > CONNECT scott/tiger@orcl
What could be the reason for this?
A. The listener is not running on the database node.
B. The TNS_ADMINenvironment variable is set to the wrong value.
C. The orcl.oracle.com database service is not registered with the listener.
D. The DEFAULT_DOMAINparameter is set to the wrong value in the sqlnet.orafile.
E. The listener is running on a different port.
Answer: C
Explanation/Reference:
Explanation:
Service registration enables the listener to determine whether a database service and its service handlers are available. A service handler is a dedicated server process or dispatcher that acts as a connection point to a database. During registration, the LREG process provides the listener with the instance name, database service names, and the type and addresses of service handlers. This information enables the listener to start a service handler when a client request arrives.

NEW QUESTION NO: 8
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/Reference:
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.

NEW QUESTION NO: 9
You executed this command to create a password file:
$ orapwd file = orapworcl entries = 10 ignorecase = N
Which two statements are true about the password file?
A. It will permit the use of uppercase passwords for database users who have been granted the SYSOPER role.
B. It contains username and passwords of database users who are members of the OSOPERoperating system group.
C. It contains usernames and passwords of database users who are members of the OSDBAoperating system group.
D. It will permit the use of lowercase passwords for database users who have granted the SYSDBArole.
E. It will not permit the use of mixed case passwords for the database users who have been granted the SYSDBArole.
Answer: A,D
Explanation/Reference:
Explanation:
* You can create a password file using the password file creation utility, ORAPWD.
* Adding Users to a Password File
When you grant SYSDBA or SYSOPER privileges to a user, that user's name and privilege information are added to the password file. If the server does not have an EXCLUSIVE password file (that is, if the initialization parameter REMOTE_LOGIN_PASSWORDFILE is NONE or SHARED, or the password file is missing), Oracle Database issues an error if you attempt to grant these privileges.
A user's name remains in the password file only as long as that user has at least one of these two privileges. If you revoke both of these privileges, Oracle Database removes the user from the password file.
* The syntax of the ORAPWD command is as follows:
ORAPWD FILE=filename [ENTRIES=numusers]
[FORCE={Y|N}] [IGNORECASE={Y|N}] [NOSYSDBA={Y|N}]
* IGNORECASE
If this argument is set to y, passwords are case-insensitive. That is, case is ignored when comparing the password that the user supplies during login with the password in the password file.

NEW QUESTION NO: 10
Which three are true about the large pool for an Oracle database instance that supports shared server connections?
A. Allocates memory for RMAN backup and restore operations
B. Allocates memory for shared and private SQL areas
C. Contains a cursor area for storing runtime information about cursors
D. Contains stack space
E. Contains a hash area performing hash joins of tables
Answer: A,B,C
Explanation/Reference:
Explanation:
The large pool can provide large memory allocations for the following:
/(B)UGA (User Global Area) for the shared server and the Oracle XA interface (used where transactions interact with multiple databases)
/Message buffers used in the parallel execution of statements
/(A) Buffers for Recovery Manager (RMAN) I/O slaves
Note:
* large pool
Optional area in the SGA that provides large memory allocations for backup and restore operations, I/O server processes, and session memory for the shared server and Oracle XA.
* Oracle XA
An external interface that allows global transactions to be coordinated by a transaction manager other than Oracle Database.
* UGA
User global area. Session memory that stores session variables, such as logon information, and can also contain the OLAP pool.
* Configuring the Large Pool
Unlike the shared pool, the large pool does not have an LRU list (not D). Oracle Database does not attempt to age objects out of the large pool. Consider configuring a large pool if the database instance uses any of the following Oracle Database features:
* Shared server
In a shared server architecture, the session memory for each client process is included in the shared pool.
* Parallel query
Parallel query uses shared pool memory to cache parallel execution message buffers.
* Recovery Manager
Recovery Manager (RMAN) uses the shared pool to cache I/O buffers during backup and restore operations. For I/O server processes, backup, and restore operations, Oracle Database allocates buffers that are a few hundred kilobytes in size.

NEW QUESTION NO: 11
In your multitenant container database (CDB) with two pluggable database (PDBs). You want to create a new PDB by using SQL Developer.
Which statement is true?
A. The CDB must be open.
B. The CDB must be in the mount stage.
C. The CDB must be in the nomount stage.
D. Alt existing PDBs must be closed.
Answer: A
Explanation/Reference:
Explanation:
* 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. The size of the seed PDB is only about 1 gigabyte and it takes only a few seconds on a typical machine to copy it.

NEW QUESTION NO: 12
You are administering a database stored in Automatic Storage management (ASM). The files are stored in the DATA disk group. You execute the following command:

What is the result?
A. The file '+data.231.45678' is physically relocated to '+data/prod' and renamed as 'myfile.dbf'.
B. The file '+data.231.45678' is renamed as 'myfile.dbf', and copied to '+data/prod'.
C. The file '+data.231.45678' remains in the same location and a synonym 'myfile.dbf' is created.
D. The file 'myfile.dbf' is created in '+data/prod' and the reference to '+data.231.45678' in the data dictionary removed.
Answer: C
Explanation/Reference:
Explanation:
ADD ALIAS
Use this clause to create an alias name for an Oracle ASM filename. The alias_name consists of the full directory path and the alias itself.

NEW QUESTION NO: 13
You notice a performance change in your production Oracle 12c database. You want to know which change caused this performance difference.
Which method or feature should you use?
A. Taking a new snapshot and comparing it with a preserved snapshot
B. Active Session History (ASH) report
C. Compare Period ADDM report
D. AWR Compare Period report
Answer: C

NEW QUESTION NO: 14
Identify three valid methods of opening, pluggable databases (PDBs).
A. ALTER PLUGGABLE DATABASE OPEN ALL ISSUEDfrom the root
B. ALTER PLUGGABLE DATABASE OPEN ALL ISSUEDfrom a PDB
C. ALTER PLUGGABLE DATABASE PDB OPENissued from the seed
D. ALTER DATABASE PDB OPENissued from the root
E. ALTER DATABASE OPENissued from that PDB
F. ALTER PLUGGABLE DATABASE PDB OPENissued from another PDB
G. ALTER PLUGGABLE DATABASE OPENissued from that PDB
Answer: A,E,G
Explanation/Reference:
Explanation:
E: You can perform all ALTER PLUGGABLE DATABASE tasks by connecting to a PDB and running the corresponding ALTER DATABASE statement. This functionality is provided to maintain backward compatibility for applications that have been migrated to a CDB environment.
A, G: When you issue an ALTER PLUGGABLE DATABASE OPEN statement, READ WRITE is the default unless a PDB being opened belongs to a CDB that is used as a physical standby database, in which case READ ONLY is the default.
You can specify which PDBs to modify in the following ways:
List one or more PDBs.

Specify ALL to modify all of the PDBs.

Specify ALL EXCEPT to modify all of the PDBs, except for the PDBs listed.


NEW QUESTION NO: 15
You must track all transactions that modify certain tables in the SALES schema for at least three years.
Automatic undo management is enabled for the database with a retention of one day.
Which two must you do to track the transactions? (Choose two.)
A. Enable supplemental logging for the database.
B. Specify undo retention guarantee for the database.
C. Create a Flashback Data Archive in the tablespace where the tables are stored.
D. Create a Flashback Data Archive in any suitable tablespace.
E. Enable Flashback Data Archiving for the tables that require tracking.
Answer: D,E
Explanation/Reference:
Explanation:
E: By default, flashback archiving is disabled for any table. You can enable flashback archiving for a table if you have the FLASHBACK ARCHIVE object privilege on the Flashback Data Archive that you want to use for that table.
D: Creating a Flashback Data Archive
/Create a Flashback Data Archive with the CREATE FLASHBACK ARCHIVE statement, specifying the following:
Name of the Flashback Data Archive
Name of the first tablespace of the Flashback Data Archive
(Optional) Maximum amount of space that the Flashback Data Archive can use in the first tablespace
/Create a Flashback Data Archive named fla2 that uses tablespace tbs2, whose data will be retained for two years:
CREATE FLASHBACK ARCHIVE fla2 TABLESPACE tbs2 RETENTION 2 YEAR;