In Oracle Database architecture, which set lists the components that belong to the physical database structure rather than the logical schema?

Introduction / Context:
This question deals with the physical database structure in Oracle. While schema objects such as tables and views define the logical layer, the physical layer is made up of files that store data and metadata on disk. Understanding the difference between logical and physical components is fundamental for Oracle Database administration and is frequently tested in interviews.

Given Data / Assumptions:

- The question is specifically about physical database structure in Oracle.
- Logical schema objects and security objects are not considered physical structures.
- Hardware components are separate from Oracle database files.

Concept / Approach:
Oracle documentation clearly states that the physical database structure consists of data files, control files, and redo log files. Data files store table and index data. Control files contain metadata used to start and maintain the database. Online redo log files store redo information to support recovery. Other entities like tables and views are logical, while CPUs and disks are hardware resources managed by the operating system, not part of the Oracle physical database itself.

Step-by-Step Solution:
Step 1: Recall the three core physical file types in Oracle: data files, control files, and online redo log files. Step 2: Review option A and see that it lists exactly those three elements, which are standard physical components. Step 3: Consider option B, which lists tables, views, and sequences, which are logical schema objects rather than physical files. Step 4: Observe that option C lists users, roles, and privileges, which relate to security and access control, not to physical storage. Step 5: Note that option D refers to hardware components such as CPUs and disks, which are not specific to Oracle database storage structures.

Verification / Alternative check:
You can verify this by looking at the database initialization parameters and Oracle documentation. The parameter CONTROL_FILES references control file locations, LOG_FILE_NAME or redo log configuration defines redo files, and DBA_DATA_FILES lists data files. These views and parameters prove that the physical database is made of these file types. Tables and views are referenced through segments and extents within the data files, not as separate files themselves.

Why Other Options Are Wrong:
Option B is incorrect because it mixes logical entities that are stored inside data files, not physical files themselves. Option C deals entirely with security entities that control who can access what, but not how data is stored. Option D describes hardware, which exists below the Oracle layer and is not part of the Oracle physical database structure. Thus, only option A correctly lists the physical components.

Common Pitfalls:
A common misunderstanding is to treat schema objects as physical files. For example, some new learners expect each table to have its own file, which is not necessarily true in Oracle. Another pitfall is ignoring the control file, even though it is critical for database startup and recovery. Confusing Oracle redo logs with operating system logs is also a mistake. Keeping these concepts clear helps in troubleshooting and backup and recovery planning.

Final Answer:
The physical database structure in Oracle is composed of data files, control files, and online redo log files.