For which two tasks can you use the DBMS_PDB.DESCRIBE procedure?

Question

Options

• Ato generate an XML metadata file that describes a non-CDB Oracle 12c database so that it
• Bto generate an XML metadata file from any unplugged PDB
• Cto determine whether an XML file describes a PDB that can be plugged into the CDB in which
• Dto generate a . pdb archive file for any PDB in the current CDB
• Eto generate an XML metadata file that describes the current plugged-in PDB

• A
  72% (36)
• B
  14% (7)
• C
  10% (5)
• D
  4% (2)

Explanation

DBMS_PDB.DESCRIBE generates XML metadata files that describe a database for plugging purposes - it works on a currently connected non-CDB (A) or the current plugged-in PDB (E), both of which require you to be actively connected to the database being described.

Why the distractors are wrong:

• B is wrong because unplugged PDBs already have their XML generated automatically by the ALTER PLUGGABLE DATABASE ... UNPLUG INTO command - DESCRIBE is not used post-unplug.
• C describes the job of DBMS_PDB.CHECK_PLUG_COMPATIBILITY, a separate procedure that validates whether an XML file is compatible with a target CDB.
• D is wrong because .pdb archive files are created via the UNPLUG INTO DDL command, not DESCRIBE.

Memory tip: Think of DESCRIBE as a snapshot tool - it only works on live, connected databases (non-CDB or active PDB) to produce the XML "passport" needed for plugging. If you need to check compatibility, that's CHECK_PLUG_COMPATIBILITY; if the PDB is already unplugged, its XML was written at unplug time.

No community discussion yet for this question.