Item 1:NItem 1:NEmployee 1:NPart 0:NCS8630 – Test # 2, Fall/2006 (Due: October 17, 2006)1) The following is an example of a Primary Key a) Customerb) OrderNumberc) Aged) PreviousEmployerse) Address2) The following is an example of a Composite Attributea) Customerb) OrderNumberc) Aged) PreviousEmployerse) Address3) The following is an example of a Multi valued Attributea) Customerb) OrderNumberc) Aged) List of PreviousEmployerse) Address4) Which of the following is an example of an Entitya) Customerb) OrderNumberc) Aged) PreviousEmployerse) Address5) Which of the following is NOT true about a weak entitya) It participates in at least one identifying relationshipsb) part of it’s primary key is the primary key of the corresponding strong entityc) typically, when we delete an instance of the strong entity, we want to cascade (automatically delete the corresponding instances of the weak entity.d) The Primary Key of a weak entity is always a surrogate (system generated)6) Which of the following is NOT true about a Composite Attribute a) It can be divided into two or more atomic attributes. b) Address and Full Name are examples of Composite Attributes c) The Primary Key of a weak entity is a composite attributes d) A composite attribute is the same as a multi-value attribute7) Which is NOT true about a Multi-value attributea) For a Table to be in 1NF, it must NOT have any multi-value attribute.b) List of Skills is an example of a multi-value attribute.c) Multi-value attributes should be placed in a separate table (at least theoretically).d) For a table to be in 3NF, it must have at least one Multi-value attribute.8) When converting a many (N) to many (N) unary relationship into tables, the recommended solution is:a) Either a FK or an associative tableb) An associative table (3rd table)c) One entity with a recursive foreign keyd) Two tables. The second table will contain the recursive relationship. 9) When converting a super/sub-class (categorization) relationship to tables, the default is:a) One table for the super class and one table for each sub-class entity.b) One big tablec) Eliminate the super class, just have one table for each sub-classd) Three tables10) When converting a one (1) to one (1) binary relationship into tables, which of the following statement is true:a. It doesn’t matter which of the two entities that you insert a Foreign Key.b. Check if one of the Foreign Keys represent a mandatory one. If so, you should insert a FK use that one to avoid null valuesc You should always place a Foreign key on both entities in order to avoid null valuesd. It is always best to create an associative table.11) When converting one (1) to many (N) binary relationship into tables, the recommended solution is usually:a. One big table with all attributes from both entities includedb. foreign key added on the Child (many side) referencing the parentc. foreign key added on the Parent (one side) referencing the childd. foreign key added on both sides (both tables)e. third table.12) Which is a good example of a ternary relationship ?a) Suppliers quotes Prices of Products and Products are Ordered to Customersb) Physicians Prescribes Drugsc) Sponsors Donate Goods to Church and Church gives goods to Charityd) Physicians Prescribes Drugs to PatientsQuestions 13-14: Given a problem specification, Circle the letter that corresponds to the best E-R Diagram.13) An Item contains one or more items and is contained in one or more Itemsa) Item 1:N0:N contains b) 1:N 1:NItem contains Itemc)Item 1:N1:N contains 14) An order has at least one order line and may have many order lines. Every order line corresponds to a specific order and at most one order.a) SuperClass: Order (Total, Disjoint), Sub-Class (OneOrderLine, ManyOrderLines) b) 1.1 1:NOrder has OrderLinec) 1.N 1:1Order has OrderLine15-16) Given the E-R diagrams, Circle the letter that corresponds to the best Problem Specification15).Employee 1:N0:N manages a) An employee can manage many employees, but is only managed by one employee.b) An employee can manage many employees, but some employees do not manage any employees at all. An employee has at least one and at most one manager.c) An employee can be managed by at most one employee. An employee also manages one employee at most.d) An employee may not manage any employees or may manage many employees. An employee is managed by at least one employee. Some employees are managed by more than one employee.16) 1.1 0:1Nurse is in charge Care Centera) A nurse may not be in charge of any Care Center or may be in charge of one or more than one Care Center. Every care center has one or more nurses in charge of it..b) Every care center has one and only one nurse in charge of it. A nurse may not be in charge of any care center. A nurse is in charge of at most one care center.c) A care center may have a nurse in charge or may not have any nurse in charge. A nurse isin charge of at most one Care Center. d) A nurse may be in charge of many care centers, but a care center only has one nurse in charge.17-22) Convert E-R Diagrams into Tables (List table name and name of attributes).Choose the best normalized solution.17) (pid, pname, qty)Part 0:N1:N containsa) Part (pid, pname, qty), Contains (pid, contains_name)b) Part (pid, pname, qty), Contains (pid, pname, qty), Contained (pid, contains_id)c) Part (pid, pname, qty), Contains (pid, contains_id)d) Part (pid, pname, qty, contain_id)18) ssn, Sname ApplicationID, Aname1:1 0:1Student submits Applicationa) Student (ssn, sname), Application (ApplicationID, Aname, sname)b) Student (ssn, sname, ApplicationID), Application (ApplicationID, Aname)c) Student (ssn, sname), Application (ApplicationID, Aname, ssn)d) Student (ssn, sname), Application (ApplicationID, Aname), Submits (ssn, ApplicationID) 19) vid, vnameitemId, iname1:N Price 1:1Vendor Quotes Itema) Vendor (vid, vname, ItemId), Item (itemId, iname)b) Vendor (vid, vname), Item (itemId, iname), PriceQuote (vname, iname, price)c) Vendor (vid, vname), Item (itemId, iname), PriceQuote (vid, itemID, price)d) Vendor (vid, vname), Item (itemID, iname, vid)20) ssn, ename, salary did, dname1:N 1:1Employees belong_to Departmenta) Employees (ssn, ename, salary), Department (did, dname), WorksIn (ssn,