Explanation
A: Setting a PDB resource plan is optional. If not specified, all sessions within the PDB are treated equally.
* In a non-CDB database, workloads within a database are managed with resource plans.
In a PDB, workloads are also managed with resource plans, also called PDB resource plans.
The functionality is similar except for the following differences:
/ Non-CDB Database
Multi-level resource plans
Up to 32 consumer groups
Subplans
/ PDB Database
Single-level resource plans only
Up to 8 consumer groups
(not B) No subplans

1.Set user tablespaces in the source database to READ ONLY.
2.From the Oracle Database 11g Release 2 {11.2.0.3) environment, export the metadata and any data residing in administrative tablespaces from the source database using the FULL=Y and TRANSPORTABLE=ALWAYS parameters. Note that the VER$ION=12 parameter is required only when exporting from an Oracle Database llg Release 2 database:
3.Copy the tablespace data files from the source system to the destination system. Note that the log file from the export operation will list the data files required to be moved.
4.Create a COB on the destination system, including a PDB into which you will import the source database.
5.In the Oracle Database 12c environment, connect to the pre-created PDB and import the dump file. The act of importing the dump file will plug the tablespace data files into the destination PDB Oracle White Paper - Upgrading to Oracle Database 12c -August 2013

Note:
*The md_restore command allows you to restore a disk group from the metadata created
by the md_backup command.
/md_restore Command
Purpose
This command restores a disk group backup using various options that are described in
this section.
/In the restore mode md_restore, it re-create the disk group based on the backup file with
all user-defined templates with the exact configuration as the backuped disk group. There
are several options when restore the disk group
full - re-create the disk group with the exact configuration
nodg - Restores metadata in an existing disk group provided as an input parameter
newdg - Change the configuration like failure group, disk group name, etc..
*The MD_BACKUP command creates a backup file containing metadata for one or more
disk groups. By default all the mounted disk groups are included in the backup file which is
saved in the current working directory. If the name of the backup file is not specified, ASM names the file AMBR_BACKUP_INTERMEDIATE_FILE.

Datapump Import impdp in 12c includes a new parameter to disable logging during data import. This option could improve performance of import tremendously during large data loads.
The TRANSFORM=DISABLE_ARCHIVE_LOGGING is used to disable logging. The value can be Y or N.
Y to disable logging and N to enable logging.
However, if the database is running with FORCE LOGGING enabled, data pump ignores disable logging request.
Note:
*When the primary database is in FORCE LOGGING mode, all database data changes are logged. FORCE LOGGING mode ensures that the standby database remains consistent with the primary database.
*force_logging V$database
A tablespace or the entire database is either in force logging or no force logging mode. To see which it is, run: SQL> SELECT force_logging FROM v$database; FOR NO