Explanation
References https://docs.oracle.com/cd/B28359_01/network.111/b28531/auditing.htm#DBSEG0622

References:
https://docs.oracle.com/cd/B28359_01/server.111/b28310/schedover004.htm#BGBJGHBH

Explanation/Reference:
Explanation:
B:
* A PDB would have its SYSTEM, SYSAUX, TEMP tablespaces. It can also contain 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 a database instance is restarted after a failure.
Incorrect:
Not 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.
Not C: There is a separate SYSAUX tablespace for the root and for each PDB.
Not F: There is a separate SYSTEM tablespace for the root and for each PDB.

Explanation/Reference:
Explanation:
* SET_TABLE_PREFS Procedure
This procedure is used to set the statistics preferences of the specified table in the specified schema.
* Example:
Using Pending Statistics
Assume many modifications have been made to the employees table since the last time statistics were gathered. To ensure that the cost-based optimizer is still picking the best plan, statistics should be gathered once again; however, the user is concerned that new statistics will cause the optimizer to choose bad plans when the current ones are acceptable. The user can do the following:
EXEC DBMS_STATS.SET_TABLE_PREFS('hr', 'employees', 'PUBLISH', 'false'); By setting the employees tables publish preference to FALSE, any statistics gather from now on will not be automatically published. The newly gathered statistics will be marked as pending.