Backing Up a Whole CDB
Backing up a whole CDB is similar to backing up a non-CDB. When you back up a whole CDB, RMAN backs up the root, all the PDBs, and the archived redo logs. You can then recover either the whole CDB, the root only, or one or more PDBs from the CDB backup.
Note:
* You can back up and recover a whole CDB, the root only, or one or more PDBs.
* Backing Up Archived Redo Logs with RMAN
Archived redo logs are the key to successful media recovery. Back them up regularly. You can back up logs with BACKUP ARCHIVELOG, or back up logs while backing up datafiles and control files by specifying BACKUP ... PLUS ARCHIVELOG.

You can use SQL*Loader to do the following:
/ (A)Manipulate the data before loading it, using SQL functions. / (D)Generate unique sequential key values in specified columns.
etc: / Load data into multiple tables during the same load session.
/Load data across a network. This means that you can run the SQL*Loader client on a
different system from the one that is running the SQL*Loader server.
/Load data from multiple datafiles during the same load session.
/Specify the character set of the data.
/Selectively load data (you can load records based on the records' values).
/Use the operating system's file system to access the datafiles.
/Load data from disk, tape, or named pipe.
/Generate sophisticated error reports, which greatly aid troubleshooting.
/Load arbitrarily complex object-relational data.
/Use secondary datafiles for loading LOBs and collections.
/Use either conventional or direct path loading. While conventional path loading is very
flexible, direct path loading provides superior loading performance.
Note:
*SQL*Loader loads data from external files into tables of an Oracle database. It has a
powerful data parsing engine that puts little limitation on the format of the data in the
datafile.

Explanation/Reference:
Explanation:
A: PGA itself is subdivided. The UGA (User Global Area) contains session state information, including stuff like package-level variables, cursor state, etc. Note that, with shared server, the UGA is in the SGA. It has to be, because shared server means that the session state needs to be accessible to all server processes, as any one of them could be assigned a particular session. However, with dedicated server (which likely what you're using), the UGA is allocated in the PGA.
C: The Location of a private SQL area depends on the type of connection established for a session. If a session is connected through a dedicated server, private SQL areas are located in the server process' PGA. However, if a session is connected through a shared server, part of the private SQL area is kept in the SGA.
Note:
* System global area (SGA)
The SGA is a group of shared memory structures, known as SGA components, that contain data and control information for one Oracle Database instance. The SGA is shared by all server and background processes. Examples of data stored in the SGA include cached data blocks and shared SQL areas.
* Program global area (PGA)
A PGA is a memory region that contains data and control information for a server process. It is nonshared memory created by Oracle Database when a server process is started. Access to the PGA is exclusive to the server process. There is one PGA for each server process. Background processes also allocate their own PGAs. The total memory used by all individual PGAs is known as the total instance PGA memory, and the collection of individual PGAs is referred to as the total instance PGA, or just instance PGA. You use database initialization parameters to set the size of the instance PGA, not individual PGAs.