Database Schema: DEPARTMENT (Code, Name, Building) EMPLOYEE (ID, First, Last, DeptCode) ASSIGNMENT (EmpID, ProjectNumber, Hours) Database Instance DEPARTMENT Code 10 Name Administration Marketin Human Resources Product Development B Buildin 40 58 EMPLOYEE ID 3443 1087 DeptCode First Luke Jessica Matt Dan Last Murdock 58 Rand 9220 10 ASSIGNMENT EmpID 3443 6518 3443 ProjectNumber Hours 20 10 20 1087 a. List the attribute(s) that make up the primary key (if one exists) in ASSIGNMENT b. List the attribute(s) that make up the primary key (if one exists) in EMPLOYEE. c. List the attribute(s) that make up the primary key (if one exists) in DEPARTMENT d. List the attribute(s) that make up the foreign key (if one exists) in ASSIGNMENT e. List the attribute(s) that make up the foreign key (if one exists) in EMPLOYEE. f. List the attribute(s) that make up the foreign key (if one exists) in DEPARTMENT g. Construct a new tuple that can be inserted into ASSIGNMENT without violating any constraints. h. Construct a new tuple that cannot be inserted into ASSIGNMENT because doing so would violate referential integrity (but would not violate any other constraints) i. Construct a new tuple that can be inserted into EMPLOYEE without violating any constraints. j. Construct a new tuple that cannot be inserted into EMPLOYEE because doing so would violate a key constraint (but would not violate any other constraints) k. Which tuples in DEPARTMENT could be removed without violating referential integrity, and which tuples in DEPARTMENT would cause referential integrity to be violated if they were removed? (Remember that you can identify each tuple by its value of the primary key attribute.)