OCP question analysis _ 007: unique constraints and Indexes

When creating a unique constraint, the OCP will forcibly create or reuse the index www.2cto.com (if no index exists in the previous column, the created index is a unique index. In this case, the index name and the constraint name are the same, and the index cannot be deleted. When unique constraint is deleted, unique index is cascaded. ② If an index already exists in the column, the previous index will be reused without changing the index type. When we delete the constraint, the associated indexes are not cascaded. However, MOS provides a method to add drop index when deleting the constraint, so that you can get it done at once: www.2cto.com alter table table_name drop constraint constraint_name drop index; OCP questions: [SQL] Q: 6 Examine the SQL statem Ent that creates ORDERS table: create table orders (SER_NO number unique, ORDER_ID NUMBER, ORDER_DATE date not null, STATUS VARCHAR2 (10) CHECK (status IN ('credentials ', 'cash '), PROD_ID number references products (PRODUCT_ID), ORD_TOTAL NUMBER, primary key (order_id, order_date )); for which columns wowould an index be automatically created when you execute the above SQL statement? (Choose two.) A. SER_NO B. ORDER_ID C. STATUS D. PROD_ID E. ORD_TOTAL F. composite index on ORDER_ID and ORDER_DATE Answer: A, F