Part of the entity-relationship diagram of Fig 3.13 of the textbook is converted to the following relational model: Department (deptName, deptCode, office, ChairFacid) Student (studld, lastName, firstName, major, credits) Enroll (Student, classNumber, grade) Class (classNumber, facld, schedule, room) ClassDetails (classNumber, deptCode, courseNumber, section) Faculty (facld, LastName, firstName, deptName, rank) Evaluation (facld, date, rater, rating) Textbook (isbn, title, publisher, publicationYear) TextbookAuthor (isbn, athours) ClassTextBook (ClassNumber, isbn1, isbn2, isbn3) Question 1) The Department entity set in the diagram does not have a facld attribute. Why does the Department table have a facld column? (A) To include the "Chairs" relationship in the relational model. (B) To include the "Employ" relationship in the relational model. Question 2) The Student entity set in the diagram does not have a major attribute. Why does the Student table have a major column? (A) To include the "Enroll" relationship in the relational model. (B) To include the "HasMajor" relationship in the relational model. Question 3) The entity-relationship diagram does not have a ClassDetails entity set. Why does the relational model have a ClassDetails table? (A) To include a many-to-many relationship of the E-R model in the relational model. (B) To include a composite attribute of the E-R model in the relational model. Question 4) The diagram does not have a TextbookAuthor entity set. Why does the relational model have a TextbookAuthor table? (A)To include a many-to-many relationship of the E-R model in the relational model. (B)To include a composite attribute of the E-R model in the relational model. Question 5) The diagram does not have an Enroll entity set. Why does the relational model have an Enroll table? (A)To include a many-to-many relationship of the E-R model in the relational model. (B)To include a composite attribute of the E-R model in the relational model