DBMS-Normalization Quiz-3

DBMS Quiz-3(Normalization)

1.The Redundancy in a table in order to improve performance is called Demoralization Normalization Boyce-Codd Normal Form None of the above 2. When is a table is said to be 3NF (choose the appropriate option) Normalization improves performance by reducing redundancy. If and only if it is in 2NF and every non key attribute is Non-transitively dependent on the primary key It involves introduction of redundancy in data None of the above 3.The best definition of normal form is (choose the correct option) A relational table is said to be in a normal form if it satisfied a certain set of constraints They are special forms, or properties, or constraints that a table scheme may possess, in order to achieve certain desired goals, such as minimizing redundancy Both a & b None 4.A table is said to be 2NF When it is in 1NF and every attribute in the row is functionally dependent on the whole key A table is said to be in the 2NF when each cell of the table contains precisely One value All of the above None of the above 5.There are _________ number of Normal forms that has been defined 5 6 4 9 6.A design is said to be in 1NF if and only if (choose all the correct options) There are no repeating groups All the key attributes are defined All attributes are dependent on the primary key All of the Above 7.The Normalization theory is based on functional dependency when? When every attribute of a table functionally dependent on each other When non key attribute is functionally dependent on the primary key None of the above 8.What is mean by Transitive dependency? . which the value in a non-key field is determined by the value in another non-Key field When every attribute of a table functionally dependent on each other None of the above 9.A relation is in 1NF if it doesn't contain any ____________? Determinants Repeating groups Null values in primary key fields Functional dependencies 10.A table is in 2NF if the table is in 1NF and what other condition is met? There are no functional dependencies. There are no null values in primary key fields. There are no repeating groups. There are no attributes that are not functionally dependent on the relation's primary key.