Which of the following is a NOT a valid reason for defining a view on a table?
-
Restrict users' access to a subset of table data
-
Ensure that rows inserted remain within the scope of a definition
-
Produce an action as a result of a change to a table
-
Provide users with an alternate view of table data
Views are used to restrict access to specific rows or columns (A), simplify complex queries (D), and ensure data integrity through CHECK OPTION (B). Producing an action in response to table changes is the purpose of triggers, not views. Views are passive queries - they select data but cannot execute procedural logic in response to changes.
Views are used to restrict access to a subset of columns/rows, provide a customized or simplified representation of underlying table data, and (via WITH CHECK OPTION) ensure inserted/updated rows stay within the view's defining criteria. None of that involves executing an action in response to a data change — that's the job of a trigger, not a view. A view is a stored query definition; it has no procedural logic to 'produce an action' as a side effect of a change. So 'Produce an action as a result of a change to a table' is correctly identified as NOT a valid reason for defining a view.