You suspect unauthorized data manipulation language (DML) operations on a particular table. You want to track users who are performing the transactions and the values used in the transactions. You…

BEFORE/AFTER INSERT, UPDATE, and DELETE triggers fire automatically on the target table without requiring any explicit call, and they expose :OLD and :NEW pseudorecords containing the affected column values. Within the trigger body you can reference USER or SYS_CONTEXT('USERENV','SESSION_USER') to identify the acting user, then INSERT the captured data into a separate audit table. This satisfies all stated requirements: automatic interception, transaction value capture, user identification, and transfer to another table for analysis.

Data Pump is a bulk export/import utility for moving data between schemas or databases and has no capability to intercept or log live DML transactions.

External tables provide read-only access to data in flat files outside the database and cannot monitor or react to DML events on internal tables.

Anonymous PL/SQL blocks must be explicitly executed by a caller and have no mechanism to fire automatically in response to DML events on a table.