Question 1
Question
1. Normalization works through a series of stages called normal forms.
Question 2
Question
2. Normalization produces a lower normal form.
Question 3
Question
3. Normalization is a process that is used for changing attributes to entities.
Question 4
Question
4. In order to meet performance requirements, you may have to denormalize portions of the database design.
Question 5
Question
5. Denormalization produces a lower normal form.
Question 6
Question
6. Normalization is a very important database design ingredient and the highest level is always the most desirable.
Question 7
Question
7. A table is in BCNF if every determinant in the table is a candidate key.
Question 8
Question
8. A table is in BCNF if every determinant in the table is a foreign key
Question 9
Question
9. A table is in fourth normal form if it is in third normal form and has no independent multivalued dependencies.
Question 10
Question
10. Relational models view the data as part of a table or collection of tables in which all key values must be identified.
Question 11
Question
11. Repeating groups must be eliminated by making sure that each row defines a single entity
Question 12
Question
12. Dependency diagrams are very helpful in getting a bird’s-eye view of all the relationships among a table’s attributes.
Question 13
Question
13. Dependencies that are based on only a part of a composite primary key are called transitive dependencies.
Question 14
Question
14. All relational tables satisfy the 1NF requirements.
Question 15
Question
15. With partial dependencies, data redundancies occur because every row entry requires duplication of data.
Question 16
Question
16. Converting a database format from 1NF to 2NF is a complex process.
Question 17
Question
17. Because a partial dependency can exist only if a table's primary key is composed of several attributes, if a table in 1NF has a single-attribute primary key, then the table is automatically in 2NF.
Question 18
Question
18. A table is in 2NF if it is in 1NF and it includes no partial dependencies.
Question 19
Question
19. It is possible for a table in 2NF to exhibit transitive dependency, where one or more nonprime attributes functionally determine other nonprime attributes.
Question 20
Question
20. A determinant is any attribute whose value determines other values within a column.
Question 21
Question
21. A dependency of one nonprime attribute on another nonprime attribute is a partial dependency.
Question 22
Question
22. Atomic attributes are attributes that can be further divided
Question 23
Question
23. Normalization should be part of the design process.
Question 24
Question
24. Normalization represents a micro view of the entities within the ERD.
Question 25
Question
25. The combination of normalization and ER modeling yields a useful ERD, whose entities may now be translated into appropriate relationship structures.
Question 26
Question
26. A good relational DBMS excels at managing denormalized relations.
Question 27
Question
27. The advantage of higher processing speed must be carefully weighed against the disadvantage of data anomalies.
Question 28
Question
28. Normalization purity is easy to sustain in the modern database environment.
Question 29
Question
29. Unnormalized database tables often lead to various data redundancy disasters in production databases.
Question 30
Question
30. Attributes should clearly define participation, connectivity, and document cardinality.
Question 31
Question
31. Repeating groups must be eliminated by making sure that each column defines a single entity
Question 32
Question
32. Dependencies can be identified with the help of the dependency diagram.
Question 33
Question
33. Data redundancies are caused by the fact that every row entry requires duplication of data