A .False. CREATE SESSION doesn’t grant DML rights.
B .True. CREATE SESSION allows login.
C .True. WITH ADMIN OPTION allows revoking from others HR granted it to.
D .True. WITH ADMIN OPTION permits granting with the same option.
E .False. Users can’t revoke their own privileges.
F .False. DDL requires additional privileges (e.g., CREATE TABLE).

A .True. Local checkpoints are allowed in PDBs.
B .False. Buffer cache is CDB-level.
C .False. Log switching is CDB-level.
D .True. Restricted session can be toggled per PDB.

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.

A .False. Limited to captured privileges, not all schema objects.
B .False. SYS is excluded from capture.
C .True. Captures indirect role privileges used.
D .True. Captures direct role privileges used.
E .False. Focus is on roles, not self-owned objects broadly.

A .True. PDBs inherit default schemas from the seed.
B .True. Metadata tablespaces (e.g., SYSTEM, SYSAUX) are created.
C .False. ADMIN1 (not ADMIN) isn’t granted SYSDBA.
D .False. No read-only requirement post-creation.
E .False. PDBs start in MOUNTED state, not open.
F .True. ADMIN1 is a local user with CONNECT role only.

Optimizer Statistics drive the cost-based optimizer’s query plans. Let’s dissect each option:
A . Optimizer Statistics are collected automatically by an automatic maintenance job that runs during predefined maintenance windows.
True. Oracle 23ai uses the AutoTask framework to gather stats automatically during maintenance windows (e.g., nightly 10 PM-2 AM). The GATHER_STATS_PROG job, managed by DBMS_AUTO_TASK_ADMIN, collects stats for stale or missing objects.
Mechanics:Controlled by STATISTICS_LEVEL=TYPICAL (default) and the DEFAULT_MAINTENANCE_PLAN. It prioritizes objects with >10% changes (stale stats) or no stats.
Practical Use:Ensures stats are current without manual intervention, critical for dynamic workloads.
Edge Case:Disabled if STATISTICS_LEVEL=BASIC or the job is manually disabled via DBMS_AUTO_TASK_ADMIN.DISABLE.
B . Optimizer Statistics are collected in real-time as data is inserted, deleted, or updated.
False. Stats aren’t updated in real-time; this would be too resource-intensive. Instead, Oracle tracks changes (e.g., via DBA_TAB_MODIFICATIONS) and updates stats periodically via AutoTask or manually. Real-time stats exist in 23ai for specific cases (e.g., GATHER_TABLE_STATS with REAL_TIME_STATS), but it’s not the default.
Why Incorrect:Real-time collection would degrade performance for OLTP systems, contradicting Oracle’s batch approach.
C . Optimizer Statistics can be manually collected at multiple levels using DBMS_STATS.GATHER_*_STATS PL/SQL procedures.
True. The DBMS_STATS package offers granular control: GATHER_TABLE_STATS, GATHER_SCHEMA_STATS, GATHER_DATABASE_STATS, etc., allowing stats collection for tables, schemas, or the entire database.
Mechanics:Example: BEGIN DBMS_STATS.GATHER_TABLE_STATS(‘HR’, ‘EMPLOYEES’); END;. Options like ESTIMATE_PERCENT and DEGREE fine-tune the process.
Practical Use:Used for immediate stats updates post-DML or for custom schedules outside maintenance windows.
Edge Case:Overuse can lock stats (e.g., FORCE=TRUE), requiring careful management.
D . Optimizer Statistics are collected by the Statistics Advisor.
False. The Statistics Advisor (new in 23ai) analyzes and recommends stats improvements but doesn’t collect them. Collection is still via DBMS_STATS or AutoTask.
Why Incorrect:It’s a diagnostic tool, not an executor.
E . Optimizer Statistics are collected automatically by Automatic Workload Repository (AWR) Snapshot.
False. AWR snapshots capture performance metrics (e.g., wait times), not optimizer stats. Stats collection is a separate process via AutoTask or manual commands.
Why Incorrect:AWR and stats collection serve distinct purposes-monitoring vs. optimization.

D .True. The Shared Pool caches data dictionary metadata (e.g., table definitions) in the Library Cache and Dictionary Cache, accessible to all processes. Others serve different purposes (e.g., Large Pool for backups).

A .False. Not all trace files indicate errors; some log normal activity.
B .True. Server processes write traces (e.g., ora_s000_123.trc) to the file system.
C .True. Background processes (e.g., ora_lgwr_123.trc) also write traces.
D .False. Names include process type and PID, not just DB name and sequence.
E .False. Traces go to DIAGNOSTIC_DEST, not necessarily FRA unless configured there.

A .False. Session limits don’t tie to password changes.
B .False. CPU limits don’t lock accounts.
C .False. No direct “logged-in days” parameter.
D .True. PASSWORD_REUSE_MAX=UNLIMITED prevents reuse.
E .True. PASSWORD_LOCK_TIME sets inactivity lockout.

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.

SQL*Loader (sqlldr) loads data from external files into Oracle tables. The command sqlldr u1/oracle TABLE=emp uses defaults since no control file is specified. Let’s evaluate:
A . It overwrites the data for Alan and adds data for Curl and Bob.
False. SQLLoader’s default mode is APPEND, not REPLACE. It doesn’t “overwrite” existing rows unless REPLACE or TRUNCATE is specified in a control file. Here, row 1, Alan, 2 exists, and SQLLoader will either skip it (if a primary key rejects duplicates) or raise an error, but it won’t overwrite. 3, Curl, 4 and 4, Bob, 4 are appended.
Mechanics:Without a control file, SQL*Loader assumes APPEND and matches columns positionally (ENO, ENAME, DN).
B . It generates a log that contains control file entries, which can be used with normal SQL*Loader operations.
True. SQL*Loader always generates a log file (e.g., emp.log) when invoked. With no control file specified, it auto-generates one internally and logs it, including entries like LOAD DATA INFILE ’emp.dat’ APPEND INTO TABLE emp FIELDS TERMINATED BY ‘,’ (ENO, ENAME, DN). This can be reused.
Practical Use:The log’s control section is editable for future runs (e.g., changing to REPLACE).
C . It appends data from EMP.DAT to EMP.
True. Default behavior without a control file is APPEND, adding new rows (3, Curl, 4 and 4, Bob, 4) to EMP. Existing rows (1, Alan, 2, 2, Ben, 2) remain unless constrained (e.g., unique key violations).
Mechanics:SQL*Loader processes each line of emp.dat, skipping duplicates if constrained, appending otherwise.
D . It generates a SQL script that it uses to load data from EMP.DAT to EMP.
False. SQL*Loader doesn’t generate SQL scripts; it uses direct path or conventional path loading, not SQL scripts. The log contains control file syntax, not a script.
E . It overwrites all data in EMP with data from EMP.DAT.
False. REPLACE or TRUNCATE would overwrite, but these require a control file with those options. Default APPEND preserves existing data.

A .True. ROW MOVEMENT must be enabled for SHRINK SPACE.
B .False. Indexes and IOTs can be shrunk with CASCADE.
C .False. No such constraint requirement.
D .True. ASSM is required for online shrinking.
E .False. No primary key requirement.

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 .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. Dispatchers are for shared servers, not dedicated.
B .False. Dedicated processes die with the session.
C .True. Direct client-server communication occurs.
D .False. No dispatchers in dedicated mode.
E .True. Listener spawns for local/remote clients.
F .True. Local logins (e.g., sqlplus /) bypass the listener.

A .True. Active (in-use) UNDO is never overwritten.
B .False. Unexpired UNDO can be reused if space is needed.
C .False. Applies to unexpired, not expired UNDO.
D .False. Only unexpired UNDO is targeted.
E .True. UNDO_RETENTION sets the retention goal for unexpired UNDO.

A .False. STOP_JOB=IMMEDIATE halts the job, not backgrounds it.
B .False. You can monitor before stopping or after restarting.
C .True. Before stopping, you can reattach with expdp attach=exp_db_full.
D .True. STOP_JOB=IMMEDIATE terminates the job instantly.

False. No such procedure exists in DBMS_AUDIT_MGMT. The package offers CLEAN_AUDIT_TRAIL and CREATE_PURGE_JOB, but nothing targets a specific policy’s records by name in this format. You can filter records in UNIFIED_AUDIT_TRAIL by policy (e.g., SELECT * WHERE UNIFIED_AUDIT_POLICIES = ‘POLICY_NAME’), but purging is all-or-nothing or time-based, not policy-specific via a single command.
Why Incorrect:This appears to be a fabricated or misinterpreted option, possibly confusing audit policy management with trail purging.
Explanation:
Unified Auditing in Oracle 23ai consolidates audit records into a single trail, managed via the DBMS_AUDIT_MGMT package. Let’s evaluate each option with extensive detail:
A : Only viewed audit records can be purged from Unified Audits.
False. There’s no concept of “viewed” audit records restricting purging. Unified Audit records (stored in UNIFIED_AUDIT_TRAIL) can be purged based on time, policy, or manual intervention, regardless of whether they’ve been viewed. This option misrepresents audit management capabilities.
Mechanics:Purging is controlled by retention policies or explicit commands, not view status. For example, records older than a set retention period (e.g., 90 days via DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_PROPERTY) are eligible for purging.
Why Incorrect:No Oracle documentation ties purging to viewing, making this a fabricated limitation.
B : Use DBMS_AUDIT_MGMT.CREATE_PURGE_JOB as a privileged user toschedule an automatic purge job.
True. This procedure creates a scheduled job to automatically purge audit records based on a retention policy or custom criteria. It’s a standard method for ongoing audit trail maintenance, requiring privileges like AUDIT_ADMIN.
Mechanics:Example: BEGIN DBMS_AUDIT_MGMT.CREATE_PURGE_JOB(AUDIT_TRAIL_TYPE => DBMS_AUDIT_MGMT.AUDIT_TRAIL_UNIFIED, JOB_FREQUENCY => ‘DAILY’, JOB_STATUS => DBMS_AUDIT_MGMT.JOB_ENABLED); END;. This schedules daily purges of old records, using the retention period set by SET_AUDIT_TRAIL_PROPERTY.
Practical Use:Ideal for production environments to prevent the audit trail from growing indefinitely (e.g., avoiding tablespace exhaustion in SYSAUX).
Edge Case:If no retention period is set, the job purges nothing until configured, highlighting the need for prior setup.
C : Only the owner of a Unified Audit Policy can purge audit records by resetting the policy.
False. Audit policies don’t have “owners” in the traditional sense; they’re created by users with AUDIT_ADMIN and managed globally. Resetting or disabling a policy (e.g., NOAUDIT POLICY my_policy) stops auditing but doesn’t purge existing records. Purging is a separate operation via DBMS_AUDIT_MGMT.
Why Incorrect:This conflates policy management with audit trail cleanup, which are distinct in Oracle.
D : Use DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL as a privileged user to manually purge audit records.
True. This procedure manually purges all Unified Audit records up to the current timestamp (or a specified time), requiring AUDIT_ADMIN privileges. It’s a one-time cleanup tool.
Mechanics:Example: BEGIN DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL(AUDIT_TRAIL_TYPE => DBMS_AUDIT_MGMT.AUDIT_TRAIL_UNIFIED, USE_LAST_ARCH_TIMESTAMP => FALSE); END;. This clears the entire trail unless restricted by a timestamp.
Practical Use:Useful for immediate space reclamation or post-incident cleanup, unlike scheduled jobs.
Edge Case:If the audit trail is large, this may require significant undo space and time, potentially impacting performance.

A .True. Integrates with MOS for patches and support.
B .True. Manages Exadata, etc.
C .True. Covers WebLogic and other middleware.
D .False. Web-based, but not built into the DB.
E .False. Can manage stopped instances via agents.

A .False. AWR doesn’t create PDBs.
B .True. AWR stats aid migration planning (e.g., performance baselines).
C .False. AWR doesn’t convert CDB to Non-CDB.
D .False. SID management isn’t AWR’s role.