1Z0-083 Question #225: Real Exam Question with Answer & Explanation

Question

Options

• Aredo logs
• Bcontrol files
• Call data dictionary metadata
• Duser-defined PL/SQL packages
• Etemporary tablespaces
• Fmandatory Oracle-supplied PL/SQL packages
• Gundo tablespaces

Explanation

Redo logs (A), control files (B), and the data dictionary metadata (C) are database-wide structures that exist exactly once in a single-instance CDB - they belong to CDB$ROOT and are shared across all pluggable databases (PDBs). Redo logs capture all changes for the entire CDB instance; control files track the physical structure of the whole database; and the master Oracle data dictionary (base tables, views, internal metadata) lives in CDB$ROOT, with PDBs accessing it via metadata links rather than maintaining their own copies.

Why each distractor is wrong:

• D (user-defined PL/SQL packages): Can be created inside any PDB, not just CDB$ROOT.
• E (temporary tablespaces): Each PDB can have - and typically does have - its own local temporary tablespace.
• F (mandatory Oracle-supplied PL/SQL packages): While these originate in CDB$ROOT, they are accessible in PDBs through object/metadata links and are considered a subset of what C already covers; they are not independently "only ever" in CDB$ROOT as a separate structural element.
• G (undo tablespaces): Since Oracle 12.2, each PDB can own its own undo tablespace (local undo mode), making this PDB-scoped, not CDB$ROOT-exclusive.

Memory tip: Think "RCD = Root's Core Database" - Redo logs, Control files, Data dictionary are the three physical/structural pillars that belong solely to CDB$ROOT because they govern the entire database instance, not any individual tenant.

No community discussion yet for this question.