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. Recovery happens on startup, not shutdown.
B .False. TRANSACTIONAL waits for commits or rollbacks, then disconnects.
C .True. New connections are blocked during shutdown.
D .True. Inactive sessions persist until shutdown completes.
E .True. Active transactions can commit before disconnection.

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

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.

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.