Choose the best answer. Examine this configuration: 1. CDB1 is an Oracle container database from an older release. 2. PDB1, PDB2, PDB3, and PDB4 are pluggable databases in CDB1. A priority list…

Question

Options

• ACDB$ROOT, PDB$SEED, PDB2, PDB1, PDB3, and PDB4
• BCDB$ROOT, PDB2, PDB1, and PDB3
• CCDB$ROOT, PDB$SEED, PDB2, PDB1, and PDB3
• DCDB$ROOT, PDB1, PDB2, PDB3, and PDB4
• ECDB$ROOT, PDB$SEED, PDB1, PDB3, PDB2, and PDB4

• A
  75% (27)
• B
  14% (5)
• C
  8% (3)
• E
  3% (1)

Explanation

Option A is correct because when upgrading an Oracle CDB with dbupgrade -L, the upgrade sequence follows a strict rule: CDB$ROOT always goes first, PDB$SEED always follows immediately after (as a mandatory system component), then PDBs are processed in priority-list order (PDB2 at priority 1, then PDB1 and PDB3 at priority 2), and finally any PDB not in the priority list (PDB4) is upgraded last - it is not skipped.

Why the distractors fail:

• B omits both PDB$SEED and PDB4 - PDB$SEED is always upgraded as part of CDB infrastructure, and PDB4, though unlisted, is still upgraded after the prioritized PDBs.
• C correctly includes PDB$SEED but drops PDB4 - the -L flag controls order, not inclusion; unlisted PDBs are upgraded last, not skipped.
• D ignores the priority list entirely, placing PDB1 before PDB2 when PDB2 has explicit priority 1.
• E reverses the priority list, upgrading PDB1/PDB3 (priority 2) before PDB2 (priority 1).

Memory tip: Think of it as "Root → Seed → Listed (in order) → Unlisted" - the -L flag is a queue jumper, not a guest list. Everyone still gets upgraded; the list just determines who goes to the front of the line.

No community discussion yet for this question.