Examine this configuration: 1. CDB1 is a container database. 2. PDB1 and PDB2 are pluggable databases in CDB1. 3. PDB1 and PDB2 are OPEN in READ WRITE mode. You execute these commands successfully…

Question

Options

• AUncommitted transactions in PDB1 have been rolled back.
• BPDB1 is closed.
• CUncommitted transactions in CDB1 and PDB1 have been rolled back.
• DCDB1 is shut down.
• ECDB1 is in MOUNT state

• A
  94% (17)
• C
  6% (1)

Explanation

Oracle CDB/PDB Close Operation

The commands executed (most likely ALTER PLUGGABLE DATABASE PDB1 CLOSE IMMEDIATE;) close only PDB1 while leaving CDB1 and PDB2 fully operational. Closing a PDB with IMMEDIATE performs a checkpoint and rolls back all uncommitted transactions within that PDB - making A correct (uncommitted transactions in PDB1 are rolled back) and B correct (PDB1 is closed).

Why the distractors are wrong:

• C is wrong because only PDB1's uncommitted transactions are rolled back - CDB1's transactions are unaffected since the CDB remains open.
• D is wrong because closing a single PDB has no effect on CDB1; the container database stays fully open and serving PDB2.
• E is wrong for the same reason - MOUNT state is a CDB-level concept (reached via SHUTDOWN + STARTUP MOUNT), not triggered by closing a single PDB.

Memory tip: Think of CDB1 as an apartment building and PDBs as individual units. Locking one apartment (closing PDB1) doesn't shut down the building (CDB1) or affect neighboring units (PDB2) - only the tenants inside that one unit (PDB1's transactions) are impacted.

No community discussion yet for this question.