1Z0-182 Sample Practice Exam Questions 2025 Updated Verified [Q24-Q40]

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. EXCLUDE=index skips all indexes, not re-creates them.
B .False. TABLE_EXISTS_ACTION=replace drops and re-creates tables.
C .True. EXCLUDE=index omits all indexes from import.
D .True. replace drops and re-creates existing tables.
E .False. Skips all indexes, not just overlapping ones.

False. All blocks in a segment use the tablespace’s block size (e.g., 8KB). While a database can have tablespaces with different block sizes (e.g., 8KB, 32KB), a single segment’s blocks are uniform, as it resides in one tablespace.
説明する：
Logical structures (e.g., segments, extents) map to physical structures (e.g., data files, blocks). Let’s dissect each option:
A : A segment can span multiple data files in some tablespaces.
True. A segment (e.g., a table or index) is a logical entity stored in a tablespace. In a smallfile tablespace (default in Oracle), a segment’s extents can span multiple data files if the tablespace has multiple files and space allocation requires it. This is common in large tables or when autoextend adds new files.
Mechanics:Oracle allocates extents across available data files in a round-robin fashion (with ASSM) or as needed, ensuring the segment’s data is distributed. This doesn’t apply to bigfile tablespaces, which use a single data file.
Example:A 10GB table in a tablespace with two 5GB data files will span both.
B : Segments can span multiple tablespaces.
False. A segment is confined to a single tablespace. Oracle enforces this to maintain logical separation (e.g., a table’s data stays in its assigned tablespace). Partitioned tables can have partitions in different tablespaces, but each partition is a separate segment.
Why Not:The segment header and extent map reside in one tablespace, preventing cross-tablespace spanning for a single segment.
C : A segment might have only one extent.
True. A segment starts with one extent upon creation (e.g., a small table or index). If no further growth occurs, it remains a single-extent segment. This is common with small objects or when INITIAL extent size suffices.
Mechanics:In locally managed tablespaces (default), the initial extent is allocated based on INITIAL or tablespace defaults (e.g., 64KB), and additional extents are added only as needed.
D : All tablespaces may have one or more data files.
False. Bigfile tablespaces are restricted to one data file (up to 128TB). Smallfile tablespaces (traditional) can have multiple data files (up to 1022), but the “all” phrasing makes this false due to bigfile exceptions.
Clarification:The question’s intent may assume smallfile tablespaces, but Oracle 23ai supports both types.

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 .False. RAC can run with one instance (degraded mode).
B .True. Possible, though not typical for RAC.
C .False. No minimum of three.
D .True. RAC instances run on separate nodes.
E .False. Instances are DB-specific in RAC.

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 .True. Auditing tracks privilege use, enforcing least privilege.
B .True. Revoking unnecessary PL/SQL access limits capabilities.
C .True. ACLs restrict network access precisely.
D .False. TRUE relaxes dictionary access, violating least privilege.
E .False. TRUE allows risky OS auth, weakening security.

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

A .False. ADR is file-based, not in a schema.
B .False. No such default exists.
C .True. ADR logs ASM diagnostics.
D .True. Supports Clusterware diagnostics.
E .False. Defaults to $ORACLE_BASE or /u01/app/oracle if unset.

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

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.
説明する：
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. Any PDB except PDB$SEED can be dropped.
B .False. Source PDBs of refreshable clones can be dropped after cloning.
C .False. Dropping an application root requires explicit handling of PDBs.
D .False. Relocation doesn’t mandate dropping the source PDB.

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.

A .False. Schema owners need EXECUTE on DBMS_FGA.
B .False. Not limited to SYSDBA.
C .True. AUDIT_ADMIN includes FGA creation rights.
D .False. No such role exists.
E .True. DBMS_FGA.ADD_POLICY requires this privilege.