Materialized Views vs. Standard Views
In an Oracle database managing a high-frequency report, why would you choose to use a materialized view over a standard view or table for performance optimization?
- A Materialized view stores precomputed query results, reducing repeated execution time.
- A Materialized view allows only read-only access, while tables allow data modifications.
- A Materialized view automatically replaces outdated records with new inserts.
- A Materialized view disables transaction logging for better performance.
- A Materialized view and a table are always identical in structure and functionality.
Logical vs. Physical Structure
Which option correctly separates the logical and physical storage components in an Oracle database? For example, which part is responsible for holding actual data versus managing user access?
- Tablespace is logical; data files are physical.
- Segments are physical; control files are logical.
- Data blocks are physical; extents are logical.
- Control files are logical; redo log files are physical.
- Tables are always physical; tablespaces are always physical.
Database Normalization
What is the main purpose of applying normalization rules such as 1NF, 2NF, and 3NF in Oracle database schema design?
- To eliminate redundant data and ensure dependencies are structured logically.
- To create as many tables as possible for easier indexing.
- To prevent the use of primary keys in database tables.
- To enable direct modification of system catalog tables.
- To ensure tablespace usage is minimized irrespective of data structure.
SYSTEM Tablespace Role
Why is the SYSTEM tablespace considered essential in an Oracle database, and what could go wrong if it is taken offline?
- SYSTEM tablespace stores the data dictionary; if offline, core database operations fail.
- SYSTEM tablespace contains user data by default, so users cannot query tables.
- SYSTEM tablespace holds only temporary objects and can be dropped and recreated anytime.
- SYSTEM tablespace is used exclusively for backup operations.
- SYSTEM tablespace manages undo segments for transaction consistency.
Clustered vs. Non-Clustered Index
Given a table with frequent range queries, what is a key difference between a clustered index and a non-clustered index in Oracle databases?
- A clustered index physically reorders table data to match the index keys.
- A non-clustered index forces data to be read sequentially from disk.
- A clustered index stores a copy of the table in each index entry.
- A non-clustered index cannot handle uniqueness constraints.
- A clustered index and a non-clustered index always require separate tablespaces.
Data Block Definition
Within Oracle's storage hierarchy, what defines a data block, and why is its size significant for database performance?
- A data block is the smallest unit of I/O, impacting how efficiently data is read from disk.
- A data block is a backup segment reserved for control file changes.
- A data block is the largest allocatable space in a tablespace.
- A data block is only relevant for redo log management, not table storage.
- A data block is synonymous with a tablespace segment.
Redo Log Files Purpose
During a database recovery scenario, what is the primary role of redo log files?
- Redo log files record all changes made to the database for recovery purposes.
- Redo log files store database user credentials temporarily.
- Redo log files provide storage for archived backups.
- Redo log files are used to manage external database connections.
- Redo log files only contain undo information from failed transactions.
Segments, Extents, and Tablespaces
Given the following hierarchy: data blocks u003C extents u003C segments. What is true regarding their relationship in Oracle's logical storage structure?
- Data blocks group into extents, and extents group into segments, which belong to a tablespace.
- Segments are smaller than extents, which are smaller than data blocks.
- Data blocks are directly mapped to physical disk partitions.
- Extents always contain one segment, but can span multiple tablespaces.
- Segments exist only within redo log files, not tablespaces.
User-Level Administration Tasks
Which task falls under user-level administration for an Oracle DBA? Suppose a new analyst joins the team and requires analytics privileges.
- Creating a new user account and assigning appropriate privileges.
- Archiving redo logs for backup management.
- Rebuilding tablespaces to improve disk performance.
- Configuring network protocols for application connectivity.
- Modifying control files to change physical database structure.
Control File Functionality
What is the principal content tracked by Oracle control files, and why is their integrity critical during startup and recovery?
- Control files maintain the database's physical structure, including data file and log locations.
- Control files store only temporary tablespace information during user sessions.
- Control files record the SQL statements executed by all users.
- Control files act as a cache for frequently accessed data blocks.
- Control files contain user password hashes for authentication.