2NF – Second Normal Form — Learn free

Self-check

Questions 1–10 of 10

1. What kind of dependency does Second Normal Form (2NF) eliminate?
Question 1A. Partial dependenciesB. Transitive dependenciesC. Multi-valued dependenciesD. Join dependenciesE. Domain dependencies
2. Which two conditions must a table satisfy to be in Second Normal Form?
Question 2A. It has a surrogate key and no foreign keysB. It is already in 1NF and every non-key attribute depends on the entire primary keyC. It is in 3NF and every determinant is a superkeyD. It has no repeating groups and no transitive dependenciesE. It has a single-column key and atomic values
3. When does the Second Normal Form rule become relevant?
Question 3A. Only when a table has more than one foreign keyB. Only when a table contains repeating groupsC. Only when a table has a composite primary keyD. Only when a table has a surrogate keyE. Only when a table stores historical data
4. What is a partial dependency?
Question 4A. An attribute that depends on another non-key attributeB. An attribute that determines a candidate keyC. An attribute that can hold more than one valueD. An attribute that depends on only part of a composite key rather than the whole keyE. An attribute that is optional and may be null
5. In a repayment table keyed by (LoanID, RepayDate), why does storing LoanAmount violate Second Normal Form?
Question 5A. Because LoanAmount is a multi-valued attributeB. Because LoanAmount depends on RepayDate aloneC. Because LoanAmount is a transitive attribute of CustomerNameD. Because LoanAmount is not atomicE. Because LoanAmount depends only on LoanID, not on the full composite key
6. What practical problem arises when LoanAmount is stored alongside every repayment record?
Question 6A. The same loan amount repeats for every repayment row and a correction requires multiple updatesB. The repayment rows can no longer be uniquely identifiedC. The loan amount becomes a multi-valued attributeD. The composite key stops being uniqueE. The repayment date must be stored as text
7. How does Second Normal Form resolve a partial dependency in the loan approval example?
Question 7A. By merging the Loan and Repayment tables into oneB. By moving attributes that depend only on LoanID into a Loan table and keeping repayment-specific attributes in the Repayment tableC. By replacing the composite key with a single surrogate keyD. By deleting the LoanAmount attribute entirelyE. By converting repayment rows into a repeating group
8. Which issue does Second Normal Form NOT address?
Question 8A. Attributes depending on only part of a composite keyB. Redundancy caused by repeating loan attributes across repayment rowsC. A non-key attribute depending on another non-key attributeD. Correct dependency structure against the whole keyE. Update anomalies caused by partial dependencies
9. According to the rule for achieving Second Normal Form, what should be done with an attribute that depends on only part of the key?
Question 9A. Mark it as a candidate keyB. Store it as a comma-separated listC. Make it part of the composite keyD. Move it into a separate table where it fully depends on that table's primary keyE. Leave it in place and add an index
10. What refinement does the move from First to Second Normal Form represent?
Question 10A. A move from relational to document storageB. A move from atomic values to summary valuesC. A move from a single table to a star schemaD. A move from transactional to analytical designE. A move from merely ensuring atomic values to ensuring correct dependency structure