A .True. Auditing tracks suspicious actions.
B .False. That's monitoring, not auditing.
C .False. Auditing detects, doesn't prevent.
D .False. Corruption is a reliability issue.
E .True. Ensures privileged user compliance.

A .True. Without DB_CREATE_ONLINE_LOG_DEST_n, redo logs and control files default to DB_RECOVERY_FILE_DEST.
B .False. If only DB_CREATE_FILE_DEST is set, redo logs and control files also use it unless overridden.
C .True. DB_CREATE_ONLINE_LOG_DEST_1 becomes the default for data files and temp files if DB_CREATE_FILE_DEST is unset.
D .True. DB_CREATE_FILE_DEST serves as the default for all file types if no log-specific parameter is set.
E .False. Data files and temp files would also use DB_CREATE_ONLINE_LOG_DEST_1 if no other parameter is specified.
F .False. No such requirement exists; DB_RECOVERY_FILE_DEST operates independently.

False. All blocks in a segment use the tablespace's block size (e.g., 8KB). While a database can have tablespaces with different block sizes (e.g., 8KB, 32KB), a single segment's blocks are uniform, as it resides in one tablespace.
Explanation:
Logical structures (e.g., segments, extents) map to physical structures (e.g., data files, blocks). Let's dissect each option:
A : A segment can span multiple data files in some tablespaces.
True. A segment (e.g., a table or index) is a logical entity stored in a tablespace. In a smallfile tablespace (default in Oracle), a segment's extents can span multiple data files if the tablespace has multiple files and space allocation requires it. This is common in large tables or when autoextend adds new files.
Mechanics:Oracle allocates extents across available data files in a round-robin fashion (with ASSM) or as needed, ensuring the segment's data is distributed. This doesn't apply to bigfile tablespaces, which use a single data file.
Example:A 10GB table in a tablespace with two 5GB data files will span both.
B : Segments can span multiple tablespaces.
False. A segment is confined to a single tablespace. Oracle enforces this to maintain logical separation (e.g., a table's data stays in its assigned tablespace). Partitioned tables can have partitions in different tablespaces, but each partition is a separate segment.
Why Not:The segment header and extent map reside in one tablespace, preventing cross-tablespace spanning for a single segment.
C : A segment might have only one extent.
True. A segment starts with one extent upon creation (e.g., a small table or index). If no further growth occurs, it remains a single-extent segment. This is common with small objects or when INITIAL extent size suffices.
Mechanics:In locally managed tablespaces (default), the initial extent is allocated based on INITIAL or tablespace defaults (e.g., 64KB), and additional extents are added only as needed.
D : All tablespaces may have one or more data files.
False. Bigfile tablespaces are restricted to one data file (up to 128TB). Smallfile tablespaces (traditional) can have multiple data files (up to 1022), but the "all" phrasing makes this false due to bigfile exceptions.
Clarification:The question's intent may assume smallfile tablespaces, but Oracle 23ai supports both types.

This command moves/renames a data file online. Let's evaluate:
A . DML may be performed on tables with one or more extents in this data file during the execution of this command.
True. Introduced in 12c and refined in 23ai, MOVE DATAFILE is an online operation, allowing DML (e.g., INSERT, UPDATE) on tables within the file. Oracle ensures consistency via redo and undo.
Mechanics:The file is copied to the new location/name while tracking changes, then switched atomically.
Practical Use:Minimizes downtime in production systems.
B . If Oracle Managed Files (OMF) is used, then the file is renamed but moved to DB_CREATE_FILE_DEST.
False. With OMF, omitting the TO clause would place the file in DB_CREATE_FILE_DEST, but here, TO '\u01/sales01.dbf' explicitly specifies the target, overriding OMF defaults.
Mechanics:OMF only applies if the destination is unspecified (e.g., MOVE DATAFILE ... without TO).
Why Incorrect:Explicit path trumps OMF behavior.
C . The tablespace containing SALES1.DBF must be altered READ ONLY before executing the command.
False. READ ONLY isn't required; the operation is online and supports active use.
Why Incorrect:Conflicts with Oracle's online move feature.
D . The file is renamed and stored in the same location.
True. The command renames /u01/sales1.dbf to /u01/sales01.dbf (correcting \u01 to /u01 as a Windows/Unix typo), keeping it in /u01/. REUSE allows overwriting if sales01.dbf exists.
Mechanics:File is copied and renamed in-place within the same filesystem directory.
E . The tablespace containing SALES1.DBF must be altered OFFLINE before executing the command.
False. Offline mode isn't needed; the online move handles activetablespaces.

A .False. LMT is default in 23ai.
B .True. Bigfile tablespaces have one data file only.
C .True. AUTOEXTEND works with bigfile data files.
D .False. Block size defaults to DB_BLOCK_SIZE (e.g., 8K).
E .False. No size comparison requirement.