[Jul-2025] 100% Actual 1Z0-182 dumps Q&As with Explanations Verified & Correct Answers [Q40-Q61]

A .False. Works with DMTs too.
B .True. LMTs use bitmaps, unlike DMT freelists.
C .False. OMF is independent of management type.
D .False. Alerts work with both.
E .True. Shrink requires LMTs with ASSM.

A .True. DBA_EXTERNAL_LOCATIONS (or prefixed variants) shows external table data sources (e.g., file paths).
B-D .False. These views cover columns or tables but not external sources specifically.

A .False. lsnrctl can start a default listener without listener.ora.
B .True. EMCC provides centralized Net Services configuration.
C .False. NetCA can run standalone, not just during installation.
D .True. Net Manager configures local naming (e.g., TNSNAMES.ORA).
E .False. Net Manager is local, not centralized like EMCC.

A .True. Background processes (e.g., PMON) start.
B .False. Consistency checks require MOUNT.
C .False. Control files open in MOUNT.
D .True. SGA is allocated at startup.
E .False. SYS access requires OPEN.

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 . 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.

A .True. Enabled per session with ALTER SESSION ENABLE RESUMABLE.
B .True. Multiple suspensions can occur in one session.
C .False. Works with dictionary-managed tablespaces too.
D .False. Timeout is session-specific.
E .True. Privilege doesn’t prevent suspension; quota limits do.
F .False. Triggers execute but can’t suspend themselves.

A .True. TIMED_STATISTICS = FALSE disables timing data collection.
B .False. No such procedure exists.
C .False. No TIMED_STATISTICS_LEVEL parameter exists.
D .True. STATISTICS_LEVEL = BASIC disables most performance monitoring.
E .False. No such procedure exists.

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.

A .False. Not real-time; collected periodically.
B .False. Not about datafile distribution.
C .True. Includes table, column, index stats for plan generation.
D .False. Stored in data dictionary, not AWR.

A .True. Enabled per session with ALTER SESSION ENABLE RESUMABLE.
B .True. Multiple suspensions can occur in one session.
C .False. Works with dictionary-managed tablespaces too.
D .False. Timeout is session-specific.
E .True. Privilege doesn’t prevent suspension; quota limits do.
F .False. Triggers execute but can’t suspend themselves.

A .False. Undo is stored in a dedicated undo tablespace, not SYSTEM.
B .True. Large transactions can span multiple undo segments.
C .False. Undo isn’t stored in SYSAUX.
D .True. Undo segments extend as needed, space permitting.
E .False. Undo doesn’t “wrap”; new extents are allocated.

Automatic Maintenance Tasks (AMTs) in 23ai optimize database performance. Let’s explore:
A .False. SQL Access Advisor exists but isn’t an AMT; it’s manual or invoked separately.
B .False. SQL Performance Analyzer assesses change impacts but isn’t part of AMTs.
C .False. No “Automatic Index Advisor” exists as an AMT; Auto Index is a separate feature.
D .True. The SPM Evolve Advisor task (part of ORA$AUTOTASK) automatically evolves SQL plan baselines, testing and accepting new plans.
Mechanics:Runs in maintenance windows, managed by DBMS_SPM.
E .True. SQL Tuning Advisor (STA) runs automatically via AMTs, tuning high-load SQL.
Mechanics:Identifies candidates from AWR and suggests indexes, profiles, etc.

A .True. PDB_DBA grants admin rights (e.g., CREATE SESSION, ALTER SYSTEM) within the PDB.
B .False. DDL on objects requires ownership or explicit grants.
C .False. User management needs CREATE USER privilege, not inherent.
D .False. It includes multiple privileges, not none.

A .False. No such restriction exists; DB_32K_CACHE_SIZE is independent of DB_CACHE_SIZE.
B .True. A nonstandard block size (32K) requires a corresponding cache (DB_32K_CACHE_SIZE) set to a non-zero value within SGA limits.
C .False. OS block size is irrelevant; Oracle manages its own block sizes.
D .False. No requirement for it to exceed DB_CACHE_SIZE.
E .True. The file system must have 100G available for the datafile.

A .False. DBCA can’t change character sets post-creation.
B .False. Listeners are managed via NetCA or lsnrctl.
C .True. DBCA can switch server modes for existing DBs.
D .False. Tablespaces are created via SQL, not DBCA for existing DBs.
E .True. DBCA can generate clone templates from existing DBs.

A .True. ADR is a file system directory structure (e.g., /u01/app/oracle/diag), external to the database.
B .False. ADR also stores diagnostics for non-database components (e.g., ASM, listener).
C .False. It’s file-based, not schema-based.
D .True. ADR logs (e.g., alert logs, trace files) are accessible even if the instance is down.
E .True. DIAGNOSTIC_DEST sets the ADR base directory.

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.

A .True. After ALTER PLUGGABLE DATABASE … UNPLUG, CDB_PDBS.STATUS shows UNPLUGGED.
B .False. UNAVAILABLE isn’t a valid status here.
C .False. REMOVED isn’t used; UNPLUGGED persists until dropped.
D .False. DISABLED isn’t a PDB state in this context.

Dynamic service registration allows a database to automatically register its services with a listener without manual configuration in LISTENER.ORA. Let’s analyze each option:
A . The definition for LISTENER_1 requires a CONNECT_DATA section to enable dynamic service registration.
False. The CONNECT_DATA section is part of a client-side TNSNAMES.ORA entry for connecting to a service, not for listener registration. Dynamic registration is handled by the database’s LREG (Listener Registration) process, which uses the LOCAL_LISTENER parameter to locate the listener’s address (e.g., host1.abc.com:1521). No CONNECT_DATA is needed in the listener address definition itself. This option confuses client connection syntax with listener configuration.
Mechanics:The listener address in TNSNAMES.ORA (LISTENER_1) is sufficient for LREG to find and register with it, as long as the listener is running at that address.
B . LISTENER_1 must also be defined in the LISTENER.ORA file to enable dynamic service registration.
False. Dynamic registration doesn’t require the listener to be explicitly defined in LISTENER.ORA. The LOCAL_LISTENER parameter pointing to LISTENER_1 (resolved via TNSNAMES.ORA) tells LREG where to register services. If the listener is running on host1.abc.com:1521, LREG will find it without a LISTENER.ORA entry. However, LISTENER.ORA is needed tostartthe listener process, but that’s separate from dynamic registration.
Practical Note:If LISTENER.ORA isn’t configured, a default listener might run on port 1521, but the question implies LISTENER_1 is operational.
C . The LREG process registers services dynamically with the LISTENER_1 listener.
True. In Oracle 23ai, the LREG background process (replacing PMON’s registration role in earlier versions) dynamically registers database services with listeners specified by LOCAL_LISTENER. Here, LOCAL_LISTENER=LISTENER_1 resolves to host1.abc.com:1521 via TNSNAMES.ORA. LREG periodically sends service information (e.g., service names, instance details) to the listener, enabling clients to connect without static configuration.
Mechanics:LREG uses the TNS alias (LISTENER_1) to locate the listener’s IP and port, registers services like orcl or orclpdb, and updates the listener’s service table. This happens automatically every 60 seconds or on significant events (e.g., instance startup).
D . Dynamic service registration cannot be used for this database instance.
False. The setup (LOCAL_LISTENER set and a valid TNSNAMES.ORA entry) explicitly supports dynamic registration. No blockers (e.g., REGISTRATION_EXCLUDED_LISTENERS) are mentioned, so LREG can function normally.
E . There are two listeners named LISTENER and LISTENER_1 running simultaneously using port 1521 on the same host as the database in LISTENERS.
False. The question mentions only LISTENER_1 in the SPFILE and TNSNAMES.ORA. There’s no evidence of a second listener (LISTENER) or a LISTENERS configuration (possibly a typo). Two listeners can’t share the same port (1521) on the same host due to port conflicts unless explicitly configured with different IPs, which isn’t indicated here.

A .True. CREATE SPFILE FROM PFILE works when idle.
B .False. Includes dynamic parameters too.
C .True. CREATE PFILE FROM SPFILE generates a PFILE.
D .False. A PFILE can start the instance if no SPFILE exists.
E .True. Dynamic parameters (e.g., DB_CACHE_SIZE) are modifiable.

A .False. DISCARD STATE isn’t tied to upgrades; it resets PDB startup behavior.
B .True. Discards saved state, reverting PDB1 to manual open mode (not auto-open) after CDB restart.
C .False. Default is not auto-open; it’s manual unless explicitly saved as OPEN.
D .False. Used for state management, not general mode changes (e.g., OPEN READ WRITE).