When performing DML operations on a view without INSTEAD OF triggers:
* Option C: Views cannot be used to add rows to an underlying table if the table has columns with NOT NULL constraints lacking default values which are not referenced in the defining query of the view.
* This is true because the view would not provide values for NOT NULL columns without defaults, leading to an error.
* Option D: Views cannot be used to add or modify rows in an underlying table if the defining query of the view contains the DISTINCT keyword.
* Using DISTINCT in the view's defining query can make the view non-updatable, as it may aggregate multiple rows into one.
* Option E: Delete statements can always be done on a table through a view.
* Deletes through a view are typically unrestricted as long as the view does not involve aggregates, DISTINCT, or similar constructs that would logically preclude determining which underlying rows should be deleted.