Which two are true about PDB archive files?

Question

Options

• ADBMS_PDB.CHECK_PLUG_COMPATIBILITY can be run against a PDB archive.
• BThey contain a PDB manifest file and all the data files in uncompressed form for a PDB.
• CThey contain all the data files only in uncompressed form for a PDB.
• DThey must be created using the DBMS_PDB package.
• EThey contain a PDB manifest file and all the data files in compressed form for a PDB.
• FThey contain all the data files only in compressed form for a PDB.

• A
  95% (41)
• D
  2% (1)
• F
  2% (1)

Explanation

Options A and E are correct because a PDB archive file (.pdb) is essentially a compressed archive that bundles two things together: the PDB manifest (an XML file describing the PDB's metadata and structure) and all of the PDB's data files in compressed form. Additionally, DBMS_PDB.CHECK_PLUG_COMPATIBILITY works against PDB archives - you can pass the archive path to this procedure to verify compatibility with a target CDB before actually plugging the PDB in.

Why the distractors are wrong:

• B is wrong because it says uncompressed - data files in an archive are compressed, not raw.
• C and F are wrong on two counts: they omit the mandatory manifest file, and C incorrectly says uncompressed.
• D is wrong because PDB archives are created via SQL (UNPLUG INTO '...pdb' or CREATE PLUGGABLE DATABASE ... AS ARCHIVE), not via the DBMS_PDB package. DBMS_PDB is for checking compatibility, not creating archives.

Memory tip: Think of a PDB archive like a .zip file for a pluggable database - it zips (compresses) the data files together with a manifest (the packing list/XML). Just as you'd check a zip's compatibility before installing software, you use DBMS_PDB.CHECK_PLUG_COMPATIBILITY to vet the archive before plugging it in.

No community discussion yet for this question.