Which three statements are true about tablespaces in a multitenant container database (CDB)?

Question

Options

• AAll PDBs and CDBs have their own UNDO tablespaces.
• BAll PDBs and CDBs have their own SYSTEM and SYSAUX tablespaces.
• CEach pluggable database (PDB) can have a temporary tablespace or a tablespace group.
• DCDBs and PDBs may share the same temporary tablespace that is present in the root container.
• EThere can be only one temporary tablespace group in a CDB.

• A
  4% (2)
• B
  2% (1)
• C
  94% (47)

Explanation

In Oracle's multitenant architecture, tablespace rules differ depending on the type and version. Choice A is false: in Oracle 12c's default shared UNDO mode, all PDBs share the single UNDO tablespace located in the CDB root (CDB$ROOT). Local UNDO - where each PDB has its own UNDO tablespace - was not introduced until Oracle 18c, making A incorrect for the default 12c configuration. Choice B is false as stated: while each PDB does indeed have its own SYSTEM and SYSAUX tablespaces (a core principle of PDB isolation), the phrase 'All PDBs and CDBs' inaccurately conflates container levels; the root container (CDB$ROOT) owns the authoritative SYSTEM and SYSAUX for the entire CDB, and administrative tablespaces are not interchangeable across the hierarchy in the way the statement implies. Choice C is true: every PDB can have its own dedicated temporary tablespace or belong to a temporary tablespace group, giving each PDB independent temporary space management. Choice D is true: PDBs that have not been assigned their own temporary tablespace will by default use the temporary tablespace defined in the CDB root, meaning the root's TEMP is shared across those PDBs. Choice E is true: within a CDB, there can be only one temporary tablespace group at the CDB root level; PDB-level temporary tablespace groups are scoped to the individual PDB, not the CDB as a whole.

No community discussion yet for this question.