1Z0-083 · Question #267
1Z0-083 Question #267: Real Exam Question with Answer & Explanation
The correct answer is C. A PDB unplugged from a container database (CDB) can be plugged into a different CDB D. A non-CDB can be converted into a PDB. E. A PDB in a remote CDB can be accessed transparently there by aggregating results from local. Options C, D, and E are correct because they reflect core PDB portability and integration features. A PDB is designed to be portable - it can be unplugged from one CDB and plugged into a different CDB (C), provided the target CDB is at the same or higher Oracle release. A non-CDB
Question
Options
- AA PDB can be plugged into a CDB only if both are of the same Oracle Database release.
- BAn unplugged PDB can be plugged into multiple CDBs simultaneously by sharing data files.
- CA PDB unplugged from a container database (CDB) can be plugged into a different CDB
- DA non-CDB can be converted into a PDB.
- EA PDB in a remote CDB can be accessed transparently there by aggregating results from local
- FA PDB created from PDB$SEED must be set to READ WRITE after loading data.
- GA PDB created from PDB$SEED must be set to READ ONLY after loading data.
Explanation
Options C, D, and E are correct because they reflect core PDB portability and integration features. A PDB is designed to be portable - it can be unplugged from one CDB and plugged into a different CDB (C), provided the target CDB is at the same or higher Oracle release. A non-CDB (traditional single-tenant database) can be migrated and converted into a PDB using the DBMS_PDB package and noncdb_to_pdb.sql script (D). A remote PDB can be accessed transparently via a proxy PDB, which acts as a local pointer to a PDB residing in a remote CDB, allowing seamless cross-CDB queries (E).
Why the distractors are wrong:
- A is too restrictive - the target CDB must be at the same or higher release, not strictly the same.
- B is false - an unplugged PDB cannot be simultaneously plugged into multiple CDBs; it can only belong to one CDB at a time.
- F and G are both wrong - a PDB created from PDB$SEED opens in READ WRITE mode (restricted) by default during provisioning; no manual state change is required after loading data, and READ ONLY is never a required final state.
Memory tip: Think of PDBs like USB drives - they plug/unplug across compatible hosts (C), old hardware can be adapted to USB format (D), and a remote drive can be mounted transparently over a network (E). You'd never share the same drive between two machines simultaneously (kills B), and the drive works read/write by default - no mode-flipping needed (kills F and G).
Topics
Community Discussion
No community discussion yet for this question.