[2026] Pass Oracle 1Z1-182 Exam in First Attempt Easily [Q34-Q55]

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.

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. No checkpoint occurs with ABORT.
B .False. Instance recovery, not media recovery, is needed.
C .True. Crash recovery rolls back uncommitted changes on startup.
D .False. Files aren’t closed cleanly with ABORT.
E .True. Shutdown doesn’t roll back; recovery does.

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.

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.
Explanation:
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 . 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 .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. Oracle 23ai uses DEFAULT_MAINTENANCE_PLAN with ORA$AUTOTASK subplan for maintenance tasks (e.g., stats gathering). Others are incorrect or speculative.

A .False. V$TABLESPACE doesn’t show free space directly.
B .False. It’s from the control file, not the data dictionary.
C .True. Renaming in MOUNT state updates DBA_DATA_FILES post-open.
D .False. DBA_TABLESPACES shows attributes, not free space directly (use DBA_FREE_SPACE).
E .True. V$TABLESPACE reflects control file data.

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.

A .True. V$ views reflect real-time memory data, not consistent snapshots.
B .True. V$FIXED_TABLE lists all V$ views.
C .True. Data comes from memory structures and data dictionary metadata.
D .False. Owned by SYS, not SYSTEM.
E .False. Some V$ views are accessible in MOUNT state.

A .False. Links can connect to non-Oracle DBs via gateways.
B .False. No such user requirement; authentication is separate.
C .False. Any user with CREATE PUBLIC DATABASE LINK can create one.
D .True. Links enable remote schema access (e.g., SELECT * FROM emp@remote).
E .False. Public links allow access, but privileges on remote objects are needed.

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 .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. Backups are configured via RMAN, not DBCA.
B .True. DBCA allows nonstandard block sizes during DB creation.
C .True. DBCA can register new DBs with EM.
D .False. Block size is fixed post-creation.
E .False. Flashback is enabled via SQL, not DBCA for existing DBs.

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 .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. Revoking from USR1 doesn’t cascade due to WITH ADMIN OPTION.
B .True. Revoking from USR2 cascades to USR3 because USR2 granted it.
C .False. DBA can revoke the full privilege, not just ADMIN OPTION.
D .False. USR1 can’t revoke from USR3 directly; only the grantor (USR2) can.
E .True. WITH ADMIN OPTION breaks the revoke chain from USR1 onward.

Roles in Oracle manage privileges efficiently. Let’s dive into each option:
A . Roles must be password protected.
False. Roles can be password-protected (e.g., CREATE ROLE mgr IDENTIFIED BY secret), but it’s optional. Non-protected roles (default) are enabled automatically if granted, requiring no password.
Mechanics:Password-protected roles need SET ROLE mgr IDENTIFIED BY secret, enhancing security for sensitive privileges.
B . Roles may be granted to other roles.
True. Roles can form hierarchies (e.g., GRANT clerk TO mgr), allowing nested privilege management.
Mechanics:A user with mgr inherits clerk privileges indirectly. Revoking clerk from mgr cascades appropriately.
Practical Use:Simplifies complex privilege structures in large organizations.
C . The SET ROLE statement can enable one or more roles for a session.
True. SET ROLE role1, role2; activates specified roles for the session, assuming they’re granted and not password-protected (or password is provided).
Mechanics:Enabled roles grant their privileges immediately within the session scope.
D . Object privileges may not be granted to roles.
False. Object privileges (e.g., GRANT SELECT ON emp TO clerk) are a primary use of roles, making this statement incorrect.
Why Incorrect:Roles are designed for this purpose, contradicting the option.
E . All roles granted to a user are set on default when the user logs in.
False. Only roles marked as DEFAULT ROLE (via ALTER USER … DEFAULT ROLE role1) are enabled at login. Non-default roles require SET ROLE.
Mechanics:Check via SELECT * FROM DBA_ROLE_PRIVS WHERE DEFAULT_ROLE=’YES’.
F . The SET ROLE statement can disable one or more roles for a session.
True. SET ROLE NONE disables all roles, or SET ROLE role1 implicitly disables others not listed, providing granular control.
Practical Use:Useful for testing or restricting privileges temporarily.

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

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.