Question 1 2 pts Composite attribute in ER model is represented in relational model as One column for each component attribute and NO column for the composite attribute One column for the composite attribute One column for each component attribute and one column for the composite attribute Separate table for component attributes Question 2 2 pts For disjoint AND complete mapping class hierarchy, a table is created for the super class entity set during mapping to relational model. True O False Question 3 2 pts For mapping one to one relationship without total participation from ER model to relational model, the following is true. There is one column for each participating entity set's primary key. The representation is ignored One extra column is augmented to the table of the entity set Question 4 2 pts For many-to-many relationships being represented in relational model, primary key of the new schema is the foreign key of relation with less cardinality. True False Question 5 2 pts During mapping weak entity sets of (E)ER model to relational model, primary key of the weak entity set is foreign key of the strong entity set discriminator plus foreign key discriminator primary key of the strong entity set Question 6 2 pts The goals for mapping a (E)ER model to Relational model are: Preserve all information Minimize null values Maintain constraints to extent possible Minimize number of tables Question 7 3 pts For non-disjoint and/or non-complete class hierarchy, which of the following statements are true when mapping from ER to relational model. O a table is created for each super class entity set according to normal entity set translation method. primary key of the subclass table is used as primary key of the new table primary key of the super class table is used as the primary key of the new table. O a table is created for each subclass entity set with a column for each of the attributes of that entity set plus one for each attributes of the primary key of the super class entity set