What is the key behavioral difference between the SQL DELETE and TRUNCATE commands when used to remove all rows from a table?

DELETE removes rows one at a time as a logged, DML operation, meaning it can typically be rolled back within a transaction and will fire any row-level triggers defined on the table. TRUNCATE, by contrast, is typically implemented as a minimally logged operation that deallocates entire data pages at once, which is why in most database systems it cannot be rolled back once committed (or is auto-committed) and does not fire row-level triggers. TRUNCATE does not remove the table's structure (that's DROP TABLE); DELETE does not require a WHERE clause (omitting it deletes all rows); and the DML/DDL classification in option C is actually reversed from how most systems categorize these commands.