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.

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.

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

B: SYSDG administrative privilege has ability to perform Data Guard operations (including startup and shutdown) using Data Guard Broker or dgmgrl.
D: SYSASM
The new (introduced in 11g) SYSASM role to manage the ASM instance, variable extent sizes to reduce shared pool usage, and the ability of an instance to read from a specific disk of a diskgroup E (Not A): SYSDBA is like a role in the sense that it is granted, but SYSDBA is a special built-in privilege to allow the DBA full control over the database Incorrect:
Not C: SYSKM. SYSKM administrative privilege has ability to perform transparent data encryption wallet operations.
Note:
Use the V$PWFILE_USERS view to see the users who have been granted administrative privileges.