You plan to move data from a flat file to a table in your database. You decide to use SQL*Loader direct path load method to perform this task. The table in which you plan to load data in an…

CHECK constraints are disabled by default during direct path load because evaluating CHECK expressions requires the SQL engine, which is bypassed in this mode.

UNIQUE constraints remain enabled during a direct path load because Oracle validates uniqueness against existing rows at the end of the load operation, ensuring no duplicate keys are inserted.

NOT NULL constraints are enforced record-by-record during direct path load because Oracle checks each incoming value as it writes data blocks, rejecting rows with missing required values.

PRIMARY KEY constraints remain enabled because a PRIMARY KEY is logically a combination of UNIQUE and NOT NULL, both of which are enforced during direct path load as described above.

FOREIGN KEY constraints are disabled by default during direct path load because referential integrity lookups require SQL engine processing that is skipped when writing directly to data blocks.