Which three descriptions are correct about the effects of the TRUNCATE command on a table? (Choose three.)

When a table is truncated, Oracle also truncates all associated indexes on that table, resetting their segment storage and high water marks along with the table itself.

TRUNCATE is a DDL operation and does not execute row-by-row processing, so DELETE triggers are never fired; only DML DELETE statements activate those triggers.

TRUNCATE does not cascade to child tables; if a parent table has a foreign key relationship, truncating the parent will fail unless the FK constraint is disabled or the child table is empty.

TRUNCATE resets the high water mark to the first usable data block in the segment, making the space immediately available for reuse and allowing full scans to skip the previously allocated but now empty blocks.

Because TRUNCATE is a DDL statement processed as a direct path operation, it generates no or negligible undo data, which is why it cannot be rolled back with a ROLLBACK statement unlike a DELETE.