A table can be in first normal form even if it still repeats order dates across multiple rows.
5 Normalization and Data Integrity Online Quiz Questions
Use this free practice quiz with 20 questions to review 5 Normalization and Data Integrity, test your knowledge, and prepare for your next test or exam.
A relation is in 1NF, and all its candidate keys contain a single attribute. What follows about its second normal form status?
- A
It has no functional dependencies.
- B
It is automatically in 2NF.
- C
Every attribute is a primary key.
- D
It has no foreign keys.
In a functional dependency, what is the database term for the attribute set that determines another attribute set?
A database design prevents staff from recording a new supplier until they also add a product supplied by that supplier. Which problem does this illustrate?
- A
Update anomaly
- B
Insertion anomaly
- C
Deletion anomaly
- D
Partial dependency
In an OrderItems table, the combination of OrderID and ProductID identifies each row. This is a .
Select all statements that accurately describe database constraints.
- A
A primary key identifies rows.
- B
A foreign key ensures that every referenced value is non-null.
- C
A foreign key ensures that references point to existing rows.
- D
A UNIQUE constraint allows duplicate values by design.
- E
NOT NULL enforces alternate uniqueness rules.
In an OrderLine table keyed by OrderID and ProductID, ProductID alone determines ProductName. What is this type of dependency called?
If every cell contains a single value, then the table cannot have any redundant data.
- A
True
- B
False
To avoid repeating supplier names for products from the same supplier, store SupplierID and SupplierName in a separate relation.
When deciding whether a product determines its supplier, what should guide the functional dependency?
- A
Infer dependencies only from repeated patterns in a small sample.
- B
Treat every attribute as determining every other attribute.
- C
Use rules that describe the real-world situation.
- D
Assume dependencies are irrelevant if a table has a primary key.
When decomposing a relation, select all design properties that should be checked.
- A
The decomposed tables can be joined without losing or inventing information.
- B
Every original attribute must appear in every resulting table.
- C
All functional dependencies must be discarded.
- D
Important dependencies can still be enforced where needed.
An OrderLine relation has attributes OrderID, ProductID, OrderDate, ProductName, SupplierID, SupplierName, and Quantity. Its key is the pair OrderID and ProductID. The business rules are: OrderID determines OrderDate; ProductID determines ProductName, SupplierID, and SupplierName; and the full key determines Quantity. Decompose this relation into tables that remove partial dependencies for 2NF, and explain how the attributes are grouped.
A database must enforce a rule that an alternate identifier cannot be duplicated, even though it is not the primary key. Which constraint is appropriate?
- A
NOT NULL
- B
UNIQUE
- C
Foreign key
- D
Check constraint
A database stores a service fee on every invoice for that service. When the fee changes, an employee updates only some of the invoice rows, leaving different fee values for the same service. What kind of anomaly does this illustrate?
- A
Deletion anomaly
- B
Update anomaly
- C
Insertion anomaly
- D
A violation of the rule that each cell contain a single value
A table stores course descriptions only on class-offering rows. If the last offering of a course is deleted, the course description disappears too. Which problem does this illustrate?
- A
Update anomaly
- B
Insertion anomaly
- C
Deletion anomaly
- D
A partial dependency
In a relation with attributes ProductID, CategoryID, and CategoryName, assume ProductID is the key, CategoryID is not a key, and ProductID determines CategoryID, which determines CategoryName. What kind of dependency involving CategoryName makes the relation fail the informal 3NF rule?
- A
A partial dependency on part of a composite key
- B
A transitive dependency through a non-key attribute
- C
A dependency on a prime attribute that violates 3NF
- D
A repeating group that violates 1NF
A relation has attributes A, B, C, and D, with exactly two candidate keys: {A,B} and {C}. Which listed nontrivial functional dependency has a determinant that is not a superkey but still satisfies the formal 3NF condition?
- A
A→D
- B
B→D
- C
AB→D
- D
B→A
True or false: A database design is guaranteed to enforce every real-world data rule merely because its relations are normalized.
- A
True
- B
False
A customer’s mailing address is stored on several order rows. After the customer moves, only some rows are changed, so the database shows two addresses. What is the name of this anomaly?
An attribute belongs to at least one candidate key in a relation. What is this attribute called?