A.WITH CHECK clause has no effect when deleting rows from the underlying table through the view.

B.Insert statements can always be done on a table through a view.

C.Views cannot be used to query rows from an underlying table if the table has a PRIMARY KEY and the PRIMARY KEY columns are not referenced in the defining query of the view.

D.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.

E.Views cannot be used to add or modify rows in an underlying table if the defining query of the view contains the DISTINCT keyword.

F.Delete statements can always be done on a table tough a view.

A.If a query filters on an indexed column then it will always be used during execution of the query

B.An INVISIBLE index is not maintained when Data Manipulation Language (DML) is performed on its underlying table.

C.An index can be created as part of a CREATE TABLE statement.

D.A UNIQUE and non-unique index can be created on the same table column

E.A DROP INDEX statement always prevents updates to the table during the drop operation

F.A descending index is a type of function-based index

A.CREATE OR REPLACE VIEW ord_vu
AS SELECT o.order_id, o.order_date, COUNT (i.line_item_id) ||
" NO OF ITEMS"
FROM orders o JOIN order_items i
ON (o.order_id = i.order_id)
GROUP BY o.order_id, o.order_date
WHITH CHECK OPTION;

B.CREATE OR REPLACE VIEW ord_vu
AS SELECT o.order_id, o.order_date, COUNT (i.line_item_id)
FROM orders o JOIN order_items i
ON (o.order_id = i.order_id)
GROUP BY o.order_id, o.order_date;

C.CREATE OR REPLACE VIEW ord_vu (order_id, order_date)
AS SELECT o.order_id, o.order_date, COUNT (i.line_item_id)
" NO OF ITEMS"
FROM orders o JOIN order_items i
ON (o.order_id = i.order_id)
GROUP BY o.order_id, o.order_date;

D.CREATE OR REPLACE VIEW ord_vu
AS SELECT o.order_id, o.order_date, COUNT (i.line_item_id)
" NO OF ITEMS"
FROM orders o JOIN order_items i
ON (o.order_id = i.order_id)
GROUP BY o.order_id, o.order_date;

A.The FIRST_NAME column would be dropped provided it does not contain any data.

B.The FIRST_NAME column can be dropped even if it is part of a composite PRIMARY KEY provided the CASCADE option is added to the SQL statement.

C.The drop of the FIRST_NAME column can be rolled back provided the SET UNUSED option is added to the SQL statement.

D.The FIRST_NAME column would be dropped provided at least one column remains in the table.

A.A UNIQUE index can be altered to be non-unique.

B.An update to a table can result in updates to any or all of the table's indexes.

C.A table belonging to one user can have an index that belongs to a different user,

D.An update to a table can result in no updates to any of the table's indexes.

E.A SELECT statement can access one or more indices without accessing any tables.

F.When a table is dropped and is moved to the RECYCLE BIN, all Indexes built on that table are permanently dropped.