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.

B .True. Without SCOPE, ALTER SYSTEM defaults to BOTH (memory and SPFILE); PFILE isn’t updated unless manually recreated.

A .True. Multiple sessions with different users are possible.
B .False. Buffer cache and redo log buffer are in SGA, not large pool.
C .True. Session tracks login state.
D .True. Each process has its own PGA.
E .False. Connection is the network link; session is the state.
F .True. Same user can have multiple sessions (e.g., via different terminals).

A .False. Recovery happens on startup, not shutdown.
B .False. TRANSACTIONAL waits for commits or rollbacks, then disconnects.
C .True. New connections are blocked during shutdown.
D .True. Inactive sessions persist until shutdown completes.
E .True. Active transactions can commit before disconnection.

A .True. Migration updates index ROWIDs.
B .True. Updates can migrate rows if space is insufficient.
C .True. Large updates can chain rows across blocks.
D .False. Chained rows may span blocks but aren’t required to.
E .False. Inserts don’t migrate; they chain if too large initially.

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.

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. External tables are read-only.
B .True. Defines how external data (e.g., CSV) is mapped to SQL.
C .False. Data is external, not in the DB.
D .False. Storage is external; Oracle doesn’t define it.

A .True. DUAL is public; any user with SELECT can query it.
B .True. One row, one VARCHAR2 column (DUMMY).
C .False. Fixed at one row.
D .False. Not restricted to SYS.
E .False. One row, one column only.
F .False. Can return expressions, not just constants.

A .False. Diagnostic collection is ADR, not AMT.
B .True. Resource Manager allocates resources to AMTs.
C .True. Scheduler defines maintenance windows.
D .False. Packaging is IPS/ADR, not AMT.
E .False. Alert log is separate from AMTs.
F .True. Tasks like stats collection are AMTs.

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.

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.

B .True. The SQL Statistics Advisor (new in 23ai) identifies stale or missing statistics. Others focus on tuning, performance analysis, or access paths.

A .False. ORCL is a TNS alias, not necessarily the DB name.
B .True. Must map to a connect descriptor (e.g., HOST=… PORT=1531) in tnsnames.ora.
C .False. It’s not the server name but a network alias.
D .False. Client-side tnsnames.ora is used, not server-side.
E .False. SERVICE_NAMES is server-side, not client-side.

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

User authentication in Oracle 23ai determines how users (especially administrative ones) connect to the database. Let’s analyze each option with extensive detail:
A . Operating System authentication may be used for system-privileged administrative users.
True. OS authentication allows users mapped to OS accounts (e.g., ops$oracle) to connect without a password, often used for administrative users like SYS or SYSTEM. This is configured by creating an externally authenticated user (e.g., CREATE USER “OPS$ORACLE” IDENTIFIED EXTERNALLY) and relies on the OS to verify identity.
Mechanics:When a user logs in via sqlplus / as sysdba, Oracle checks the OS user against the dba group (Unix) or ORA_DBA (Windows). If matched, no password is needed, leveraging OS security.
Practical Use:Common for DBAs managing local instances, reducing password management overhead.
Edge Case:Requires REMOTE_LOGIN_PASSWORDFILE=NONE for exclusive OS auth, but this isn’t mandatory if a password file exists alongside.
Historical Note:Introduced in early Oracle versions, this remains a robust option in 23ai for local admin access.
B . Password authentication must be used for system-privileged administrative users.
False. “Must” is incorrect; password authentication (e.g., sqlplus sys/password) is an option, not a requirement. OS authentication or password file authentication can also be used for users like SYS. This option overstates the necessity of password-based login.
Why Incorrect:Oracle’s flexibility allows multiple methods, contradicting the absolute phrasing here.
C . Password File authentication is supported for any type of database user.
False. Password file authentication is restricted to users with SYSDBA, SYSOPER, or similar system privileges (e.g., SYSBACKUP). Regular users (e.g., HR) can’t use the password file (orapw<sid>); they rely on database authentication (passwords stored in the DB) or external methods.
Mechanics:The password file stores hashed credentials for privileged users, checked during remote AS SYSDBA logins.
Why Incorrect:Extending this to “any user” ignores Oracle’s security model limiting password file usage.
D . REMOTE_LOGIN_PASSWORDFILE must be set to EXCLUSIVE to permit password changes for system-privileged administrative users.
False. REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE allows a dedicated password file for one instance, enabling password changes via ALTER USER SYS IDENTIFIED BY newpass. However, SHARED mode also permits changes for SYS, though not for other users added to the file. The “must” overstates the requirement; it’s sufficient, not necessary.
Mechanics:EXCLUSIVE locks the file to one DB, while SHARED allows multiple DBs to use it, with restrictions on non-SYS users.
E . Password File authentication must be used for system-privileged administrative users.
True. For remote administrative access (e.g., sqlplus sys/password@orcl as sysdba), a password file is mandatory when REMOTE_LOGIN_PASSWORDFILE is EXCLUSIVE or SHARED. Local OS authentication is an alternative, but for network-based admin tasks, the password file is required, making this statement true in that context.
Mechanics:Set via orapwd (e.g., orapwd file=orapworcl password=oracle entries=10), enabling remote SYSDBA logins.
Edge Case:If REMOTE_LOGIN_PASSWORDFILE=NONE, only OS auth works locally, but this isn’t the default or typical setup.

To change a PDB_MODIFIABLE parameter, the PDB must be in READ WRITE mode, allowing ALTER SYSTEM commands to modify parameters stored in the PDB’s SPFILE or memory. READONLY modes prevent modifications, and no RESTRICTED WRITE ONLY mode exists.

False. No “Automatic Application Tracing” exists as an AWR tool. SQL tracing (e.g., DBMS_MONITOR) is manual, and high-load SQL is captured by AWR indirectly via V$SQL snapshots, not a distinct tracing tool.
Why Incorrect:Conflates manual tracing with AWR’s passive collection.
Explanation:
The Automatic Workload Repository (AWR) is a cornerstone of Oracle’s self-tuning capabilities, collecting and storing performance statistics for analysis. Let’s dissect each option:
A : Automatic capture of statistical information from the SGA and storing it in the AWR using Automatic Database Diagnostic.
True. AWR automatically captures statistics (e.g., wait events, SQL stats) from the System Global Area (SGA) via the MMON (Manageability Monitor) process, storing them in the AWR repository (in SYSAUX). This is part of the Automatic Database Diagnostic Monitor (ADDM) framework, though “Automatic Database Diagnostic” likely refers to this broader mechanism.
Mechanics:Snapshots are taken hourly by default (configurable via DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS), persisting data like DBA_HIST_SYSSTAT for self-tuning analysis.
Practical Use:Enables historical performance tracking, feeding tools like ADDM and SQL Tuning Advisor.
Edge Case:If STATISTICS_LEVEL=BASIC, AWR collection is disabled, haltingself-tuning.
Historical Note:Introduced in 10g, enhanced in 23ai for finer granularity.
B : ADDM, a server-based expert that reviews database performance statistics captured by Snapshots to identify potential problems before system performance degrades noticeably.
True. The Automatic Database Diagnostic Monitor (ADDM) analyzes AWR snapshots to proactively detect issues (e.g., high CPU usage, I/O bottlenecks) and recommend fixes. It runs automatically after each snapshot in maintenance windows.
Mechanics:ADDM uses DBA_ADVISOR_FINDINGS to log issues, leveraging AWR data like DBA_HIST_SQLSTAT. Example: It might suggest adding an index for a slow query.
Practical Use:Prevents performance degradation in production systems by catching trends early.
Edge Case:Limited by snapshot frequency; real-time issues may need manual intervention.
C : Automatic Diagnostic Collector used to capture and store database errors and hung analysis.
False. No such tool exists as an “Automatic Diagnostic Collector” in AWR context. This likely confuses the Incident Packaging Service (IPS) or ADR (Automatic Diagnostic Repository), which handles errors but isn’t AWR-based or self-tuning.
Why Incorrect:ADR collects trace files and logs, not AWR statistics, and isn’t part of self-tuning.
D : Automatic population of performance views (V$ views) from statistical data stored in AWR repository and using Automatic Database Diagnostic.
False. V$ views (e.g., V$SESSION) are real-time memory structures in the SGA, not populated from AWR, which is historical (e.g., DBA_HIST_*). AWR doesn’t back-feed V$ views; the reverse occurs via snapshots.
Why Incorrect:Misunderstands the data flow; AWR is a sink, not a source for V$ views.

Dictionary-managed tablespaces (DMTs) use the data dictionary for extent management, whilelocally managed tablespaces (LMTs) use bitmaps. Let’s evaluate compatibility:
A . Capacity planning growth reports based on historical data in the Automatic Workload Repository (AWR).
True. AWR tracks space usage (e.g., DBA_HIST_TBSPC_SPACE_USAGE) regardless of tablespace type, enabling growth reports for both DMTs and LMTs.
Mechanics:MMON collects metrics like segment growth, stored in SYSAUX, accessible via EM or scripts.
Practical Use:Helps predict when to add data files, universal across management types.
B . Online table segment shrink.
False. ALTER TABLE … SHRINK SPACE requires LMTs with Automatic Segment Space Management (ASSM), unavailable in DMTs, which lack bitmap-based free space tracking.
Why Incorrect:DMTs use freelists, incompatible with shrink operations.
C . Online index segment shrink.
False. Like tables, ALTER INDEX … SHRINK SPACE requires LMTs with ASSM, not supported in DMTs.
Why Incorrect:Same limitation as B; DMTs can’t compact online.
D . Oracle Managed Files (OMF).
True. OMF automates file naming and placement (via DB_CREATE_FILE_DEST) for both DMTs and LMTs, agnostic to extent management.
Mechanics:Example: CREATE TABLESPACE ts1; creates an OMF file in either type.
Edge Case:DMTs are rare in 23ai, but OMF still applies.
E . Automatic data file extension (AUTOEXTEND).
True. AUTOEXTEND ON allows data files to grow as needed, supported in both DMTs and LMTs since early versions.
Mechanics:ALTER DATABASE DATAFILE … AUTOEXTEND ON NEXT 100M; works universally.

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.

A . Dependent indexes become UNUSABLE.False. SHRINK SPACE COMPACT does not affect index usability; only SHRINK SPACE without COMPACT may require index maintenance if CASCADE is omitted.
B . … starting toward the end of the ORDERS segment.False. Rows are compacted toward the beginning of the segment, not the end.
C . Only queries are allowed …False. Both queries and DML are allowed during SHRINK SPACE COMPACT as it’s an online operation.
D . The high-water mark (HWM) of ORDERS is adjusted.False. COMPACT moves rows but doesn’t adjust the HWM; the full SHRINK SPACE command is needed for HWM adjustment.
E . Queries and DML statements are allowed …True. This is an online operation in 23ai, allowing concurrent access.
F . … starting from the beginning of the ORDERS segment.True. Rows are moved to fill free space from the segment’s start.

A .False. Data files open in OPEN.
B .False. Redo logs open in OPEN.
C .False. PFILE/SPFILE is read at NOMOUNT.
D .False. SGA is allocated at NOMOUNT.
E .True. Alert log records mount event.
F .True. Control files are read in MOUNT.