1Z0-083 · Question #68
Which two are true about creating container databases (CDBs) and pluggable databases (PDBs) in Oracle 19c and later releases?
The correct answer is A. A CDB can be duplicated using the Database Configuration Assistant (DBCA) in silent mode. D. A PDB snapshot can be a sparse copy of a source PDB. Option A is correct because DBCA supports CDB duplication in silent (non-interactive) mode using command-line parameters, making it a valid and documented method for automating CDB creation. Option D is correct because PDB snapshots introduced in Oracle 12.2+ can be sparse…
Question
Which two are true about creating container databases (CDBs) and pluggable databases (PDBs) in Oracle 19c and later releases?
Options
- AA CDB can be duplicated using the Database Configuration Assistant (DBCA) in silent mode.
- BA CDB can be duplicated using Recovery Manager (RMAN) with no configuration required before
- CA PDB snapshot must be a full copy of a source PDB.
- DA PDB snapshot can be a sparse copy of a source PDB.
- EA CDB can be duplicated only by using the Database Configuration Assistant (DBCA).
How the community answered
(54 responses)- A93% (50)
- B4% (2)
- C2% (1)
- E2% (1)
Explanation
Option A is correct because DBCA supports CDB duplication in silent (non-interactive) mode using command-line parameters, making it a valid and documented method for automating CDB creation.
Option D is correct because PDB snapshots introduced in Oracle 12.2+ can be sparse copies (thin clones) - they reference unchanged blocks from the source PDB rather than copying all data, saving significant storage space. This is done using SNAPSHOT COPY clause with compatible storage (e.g., ACFS or NFS).
Why the distractors are wrong:
- B is false because RMAN does require pre-configuration to duplicate a CDB - at minimum you need a password file, auxiliary connection setup, and initialization parameters for the target.
- C is the direct opposite of D - PDB snapshots are specifically valuable because they don't need to be full copies; a sparse copy is a core feature.
- E is false because DBCA is not the only method; RMAN duplication is also a fully supported approach for copying CDBs.
Memory tip: Associate "DBCA = Deployable Quietly (silent mode)" and "PDB Snapshots = Sparse, not Stuffed" - the snapshot's whole point is efficiency through sparseness, not copying everything.
Topics
Community Discussion
No community discussion yet for this question.