Which of the following is the correct syntax to create a table with a foreign key constraint in SQL?  *1 pointCREATE TABLE orders (order_id INT PRIMARY KEY, customer_id INT, FOREIGN KEY(customer_id) REFERENCES customers(customer_id))CREATE TABLE orders (order_id INT PRIMARY KEY, customer_id INT REFERENCES customers(customer_id))CREATE TABLE orders (order_id INT PRIMARY KEY, customer_id INT, CONSTRAINT fk_customer FOREIGN KEY(customer_id) REFERENCES customers(customer_id))CREATE TABLE orders (order_id INT PRIMARY KEY, customer_id INT, CONSTRAINT fk_customer REFERENCES customers(customer_id))

______ is NOT a type of constraint in SQL language?FOREIGN KEYPRIMARY KEYUNIQUEALTERNATE KEY

Given the following statements: S1: A foreign key declaration can always be replaced by an equivalent check assertion in SQL. S2: Given the table R(a,b,c) where a and b together form the primary key, the following is a valid table definition. CREATE TABLE S ( ConstINTEGER, d INTEGER, e INTEGER, PRIMARY KEY (d), FOREIGN KEY (a) references R) Which one of the following statements is CORRECT?

For relation having schema as follows:Student(rollno number, name varchar2, address varchar2, age number, regno number)Which of the following is the correct way to create a table in the database?*1 pointcreate table student(rollno number[6], name varchar2[20], address varchar2[20], age number[3], regno number[10])create table student(rollno number[6], name varchar2[20], address varchar2[20], age number[3], regno number[10]);create table Student(rollno number[6], name varchar2[20], address varchar2[20], age number[3], regno number[10])None of the above

4. Describe the process of creating a foreign key constraint in MySQL, and why is it important in maintaining data integrity across tables.

To create a relationship between two tables, the attributes that define the primary key in one table must appear as attributes in another table, where they are referred to as a foreign key