Oracle Database 23ai Administration Associate Practice Tests and PDFs

The ALTER DATABASE MOVE DATAFILE command relocates a data file to a new location while the database remains online, introduced in Oracle 12c and enhanced in subsequent releases like 23ai. Let’s evaluate each option: A . DML may be performed on tables with one or more extents in this data file during the execution of this command.True. The move operation is online by default in Oracle 23ai, allowing DML (INSERT, UPDATE, DELETE) operations on tables within the data file being moved. The database ensures consistency using redo and undo mechanisms. B . It overwrites any existing file with the name sales02.dbf in /u02 by default.False. By default, the command does not overwrite an existing file unless the REUSE clause is specified (e.g., ALTER DATABASE MOVE DATAFILE ... REUSE). Without it, the command fails if the target file exists. C . The "TO" clause containing the new file name must be specified even if Oracle Managed Files (OMF) is used.False. When OMF is enabled (via DB_CREATE_FILE_DEST), the TO clause is optional. If omitted, Oracle automatically generates a file name and places it in the OMF destination. D . Compressed objects in sales01.dbf will be uncompressed in sales02.dbf after the move.False. The move operation is a physical relocation of the data file; it does not alter the logical structure or compression state of objects within it. Compressed data remains compressed. E . Tables with one or more extents in this data file may be queried during the execution of this command.True. The online nature of the move allows queries (SELECT statements) to proceed without interruption, leveraging Oracle’s multi-version consistency model. Reference:Oracle Database Administrator’s Guide 23ai, Chapter "Managing Data Files and Temp Files," Section "Moving Data Files Online."

A . Free space is managed using freelists.False. The SEGMENT SPACE MANAGEMENT AUTO clause specifies Automatic Segment Space Management (ASSM), which uses bitmaps to track free space, not freelists (used in Manual Segment Space Management). B . It uses the database default block size.True. The BLOCKSIZE clause is not specified in the command, so the tablespace inherits the database’s default block size (typically 8K unless altered via DB_BLOCK_SIZE). C . It must be smaller than the smallest BIGFILE tablespace.False. There’s no such restriction; SMALLFILE and BIGFILE tablespaces differ in structure (multiple vs. single data file), not mandated size relationships. D . It is a locally managed tablespace.True. In Oracle 23ai, all tablespaces created without an explicit EXTENT MANAGEMENT DICTIONARY clause are locally managed by default, using extent allocation bitmaps in the data file headers. E . Any data files added to the tablespace must have a size of 5 gigabytes.False. The initial data file is 5G, but additional data files can have different sizes when added using ALTER TABLESPACE ... ADD DATAFILE. Reference:Oracle Database SQL Language Reference 23ai, "CREATE TABLESPACE" syntax; Oracle Database Administrator’s Guide 23ai, "Managing Tablespaces."

With OMF enabled, Oracle automatically manages file creation. The command ALTER TABLESPACE sales_q1 ADD DATAFILE without a file specification relies on initialization parameters: A . Specify a path in the DATAFILE clause ... with at least 100 MB of available space.False. With OMF, explicitly specifying a path overrides OMF behavior, but it’s not required for success if OMF parameters are set correctly. B . Add the AUTOEXTEND ON clause with NEXT set to 100M.False. AUTOEXTEND is optional and affects file growth, not the initial creation success, which depends on available space in the OMF location. C . Ensure that DB_RECOVERY_FILE_DEST and DB_CREATE_FILE_DEST each specify locations with at least 50 MB of available space.True. If both parameters are set,Oracle may use either for data files (depending on context), and sufficient space (e.g., 50 MB minimum for a smallfile) ensures success. D . Ensure that DB_CREATE_FILE_DEST specifies a location with at least 100 MB of available space.True. This is the primary OMF parameter for data files; sufficient space (typically 100 MB minimum for a new file) guarantees the command succeeds. E . Ensure that DB_RECOVERY_FILE_DEST and DB_CREATE_FILE_DEST each specify locations with at least 50 MB of available space.False. This is redundant with C; only one needs sufficient space, though C’s phrasing makes it a valid independent action. Reference:Oracle Database Administrator’s Guide 23ai, "Using Oracle Managed Files."

Temp UNDO, introduced in Oracle 12c and refined in 23ai, stores undo for global temporary tables (GTTs) in temporary tablespaces: A . It permits DML on GTTs even if the database is opened read-only.False. In read-only mode, DML on GTTs is allowed regardless of temp UNDO, as GTT data is session-private, but temp UNDO doesn’t specifically enable this. B . It reduces the amount of UNDO stored in the UNDO tablespace.True. Temp UNDO stores undo in the temporary tablespace, reducing usage of the permanent UNDO tablespace. C . It reduces I/Os to the SYSTEM tablespace.True. By avoiding permanent undo, it reduces metadata updates in the SYSTEM tablespace related to undo management. D . It reduces the amount of redo generated.True. Temp UNDO changes are not redo-logged to the same extent as permanent undo, minimizing redo generation. E . It reduces I/Os to the SYSAUX tablespace.False. SYSAUX is unrelated to undo management; temp UNDO affects temporary and SYSTEM tablespaces. Reference:Oracle Database Concepts 23ai, "Temporary Undo."

A .Incorrect syntax and view (pdb_spfile$ is not a valid view; PDB_SPFILE$ exists but lacks value$). B .From CDB root, V$PARAMETER shows all parameters, not PDB-specific ones. C .pdb_spfiles is not a valid view; PDB_SPFILE$ exists but requires scoping to a PDB. D .True. From the PDB, V$PARAMETER shows parameters specific to that PDB, including inherited and PDB-modified values, with ISPDB_MODIFIABLE indicating alterability. Reference:Oracle Multitenant Administrator’s Guide 23ai, "Managing PDB Initialization Parameters."