Which of the following best describes the Second Normal Form (2NF) in database normalization?
Recall that 2NF builds on 1NF by focusing on how attributes depend on the primary key.
2NF requires that the table is already in 1NF and that every non-key attribute depends on the whole primary key, not just part of it. This eliminates partial dependency.
Consider a table with a composite primary key (StudentID, CourseID) and attributes: StudentName, CourseName, and Grade. Which attribute violates 2NF?
Think about which attributes depend on only part of the composite key.
StudentName depends only on StudentID, not on CourseID, so it is partially dependent and violates 2NF.
Given a table with primary key (OrderID, ProductID) and attributes: OrderDate, ProductName, Quantity, and SupplierName. Which attribute(s) cause the table to not be in 2NF?
Consider which attributes depend on only part of the composite key.
ProductName and SupplierName depend only on ProductID, not on the full key, causing partial dependency and violating 2NF.
Which statement correctly contrasts First Normal Form (1NF) and Second Normal Form (2NF)?
Think about what each normal form focuses on.
1NF ensures atomicity of data (no repeating groups), while 2NF eliminates partial dependencies on parts of a composite key.
Why can partial dependency in a table with a composite primary key lead to data anomalies?
Consider how partial dependency affects update operations.
Partial dependency means some attributes depend only on part of the key, so updating those attributes may require multiple rows to be changed, risking inconsistency.