Transportable tablespaces were introduced in Oracle 8i to allow whole tablespaces to be copied between databases in the time it takes to copy the datafiles. It is supported in Oracle 11g.
Incorrect Answers:
A: Using Transportable database with the "FULL=Y TRANSPORTABLE=ALWAYS VERSION=12" parameters allows you to plug in an 11.2.0.3 or later non-CDB 11g database, not an 11.2.0.2.0 database.
D: The DBMS_PDB package allows you to generate an XML metadata file from a non-CDB 12c database. This allows the non-CDB to be plugged in as a PDB into an existing CDB. However, the non-CBD is an 11g (11.2.0.2.0) database.

* 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 "Database Smart
Flash Cache" 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 "DB Smart Flash Cache"
/dev/sda - size 32G
/dev/sdb - size 32G
/dev/sdc - size 64G
New view V$FLASHFILESTAT - it's used to determine the cumulative latency and read counts of
each file|device and compute the average latency

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

Explanation
A:
1. Get the list of all datafiles.
Note: RMAN Backup of ASM Storage
There is often a need to move the files from the file system to the ASM storage and vice versa. This may come in handy when one of the file systems is corrupted by some means and then the file may need to be moved to the other file system.
D: Migrating a Database into ASM
* To take advantage of Automatic Storage Management with an existing database you must migrate that database into ASM. This migration is performed using Recovery Manager (RMAN) even if you are not using RMAN for your primary backup and recovery strategy.
* Example:
Back up your database files as copies to the ASM disk group.
BACKUP AS COPY INCREMENTAL LEVEL 0 DATABASE
FORMAT '+DISK' TAG 'ORA_ASM_MIGRATION';