A .True. Captures unused self-owned object privileges.
B .False. SYS is excluded from capture.
C .False. No exclusion option for admin users.
D .False. Direct role grants aren’t separately analyzed.
E .True. Tracks indirect role privileges used.
F .True. Identifies used self-owned privileges.

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

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.

A .False. Net Manager is local, not centralized.
B .False. NetCA can run standalone.
C .True. EMCC manages service names centrally.
D .True. EMCC configures listeners on managed targets.
E .False. lsnrctl starts a default listener if no listener.ora exists.
F .True. Net Manager configures local tnsnames.ora.

A .False. Connect Time Failover doesn’t need TAF; TAF is for runtime failover.
B .False. Source Routing doesn’t mandate encryption.
C .True. Needs multiple addresses (e.g., (ADDRESS_LIST=…)) for failover.
D .False. Load balancing works with tnsnames.ora, no name server required.
E .True. Balances connections across shared server dispatchers.

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.

A .False. Not limited to CDB; PDBs can use common policies.
B .True. Common policies apply at CDB level.
C .False. Application Root uses app-specific policies.
D .False. “COMMON option” isn’t a feature; policies are common by creation context.
E .True. A common user can create policies for PDBs.

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.

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.

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.

Unified Auditing is enabled at database creation or migration in 23ai. Let’s analyze:
A . By querying V$OPTION for parameter Unified Auditing.
True. SELECT VALUE FROM V$OPTION WHERE PARAMETER = ‘Unified Auditing’; returns TRUE if enabled. It’s the definitive way to confirm Unified Auditing is active at the database level.
Mechanics:V$OPTION reflects compiled-in features; TRUE indicates the binary was linked with Unified Auditing (uniauflt=on during relink).
Practical Use:Quick, reliable check post-migration or upgrade.
B . By using the LSINVENTORY Command to query the Oracle Database Software Library.
False. LSINVENTORY (from OPatch) lists installed software components, not runtime features like auditing mode.
C . By querying the DBA_UNIFIED_AUDIT_OPTION view.
False. This view doesn’t exist; DBA_AUDIT_POLICIES or UNIFIED_AUDIT_TRAIL show policies and records but not migration status.
D . By executing DBMS_AUDIT_MGMT PL/SQL package in Verify mode.
False. No “Verify mode” exists in DBMS_AUDIT_MGMT; it manages audit trails, not migration validation.

D .True. The .pdb file (archive) contains the manifest and data files; all must be copied to the target CDB for plugging.
A-C .False. The archive alone isn’t enough; all components are needed.

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.