A data analyst is tasked with loading data into a Snowflake table 'ORDERS' with the following structure: 'CREATE TABLE ORDERS ( ORDER ID INT, CUSTOMER ID INT, ORDER DATE DATE, TOTAL_AMOUNT The data analyst needs to ensure that 'ORDER ID' is unique and not null, 'CUSTOMER ID' references a valid customer in the 'CUSTOMERS' table (column name 'CUSTOMER ID'), and 'ORDER DATE' is not in the future. Which of the following combination of constraints is the most efficient and appropriate way to enforce these Fules in Snowflake? 'CREATE TABLE CUSTOMERS ( CUSTOMER ID INT PRIMARY KEY, CUSTOMER_NAME VARCHAR(255));'.

Correct Answer: E
Option E is the most appropriate and efficient. Using a PRIMARY KEY implies an index which while beneficial for joins isn't necessary if simple uniqueness and not null are the primary requirement. A CHECK constraint 'ORDER_DATE <= is the best way to prevent future dates as TRIGGER is not available and view doesn't prevent data from being ingested.