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.

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

A :True. Dispatchers return responses to clients.
B :False. Dispatchers manage queues, not write directly.
C :False. Responses are connection-specific, not broadcast.
D :True. Dispatchers receive client requests.
E :False. Queues are common, not per-connection.

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 .True. CREATE SPFILE FROM PFILE works when idle.
B .False. Includes dynamic parameters too.
C .True. CREATE PFILE FROM SPFILE generates a PFILE.
D .False. A PFILE can start the instance if no SPFILE exists.
E .True. Dynamic parameters (e.g., DB_CACHE_SIZE) are modifiable.

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.

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.

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 .True. Enabled per session with ALTER SESSION ENABLE RESUMABLE.
B .True. Multiple suspensions can occur in one session.
C .False. Works with dictionary-managed tablespaces too.
D .False. Timeout is session-specific.
E .True. Privilege doesn’t prevent suspension; quota limits do.
F .False. Triggers execute but can’t suspend themselves.

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.

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.

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.

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 .True. PDB_DBA grants admin rights (e.g., CREATE SESSION, ALTER SYSTEM) within the PDB.
B .False. DDL on objects requires ownership or explicit grants.
C .False. User management needs CREATE USER privilege, not inherent.
D .False. It includes multiple privileges, not none.

A .False. lsnrctl can start a default listener without listener.ora.
B .True. EMCC provides centralized Net Services configuration.
C .False. NetCA can run standalone, not just during installation.
D .True. Net Manager configures local naming (e.g., TNSNAMES.ORA).
E .False. Net Manager is local, not centralized like EMCC.

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 .False. IOTs require immediate segment creation.
B .False. SYS-owned tables don’t use deferred creation.
C .True. Default since 11gR2, continued in 23ai.
D .True. Indexes inherit this attribute unless overridden.
E .True. Sessions can alter this via DEFERRED_SEGMENT_CREATION.