Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Order(OrderID, Item1, Item2, Item3) | AProduct(ProductID, ProductName, Price) OrderLine(OrderID, ProductID, Qty) | |
| 2OrderLine(OrderID, ProductID, ProductName, Qty) | BHouseName depends on HouseID, which is not the key. This transitive dependency means the table is not in 3NF. | |
| 3Step 3 to reach 3NF: remove a transitive dependency by moving the non-key determinant into its own table | CAn unnormalised table with a repeating group of item columns that must be removed to reach 1NF | |
| 4Choosing keys for new tables: the attribute that determined the moved fields becomes the new table's primary key and stays as a foreign key in the old one | DProductName depends only on ProductID, part of the composite key, so this has a partial dependency and fails 2NF | |
| 5Student(StudentID, Name, HouseID, HouseName) so the table is now in 3NF | EStudent(StudentID, Name, HouseID) House(HouseID, HouseName, HeadOfHouse) | |
| 6Normalise to 3NF: remove transitive dependencies first, then repeating groups, then partial dependencies | FThe steps are in the wrong order. Normalisation removes repeating groups (1NF), then partial dependencies (2NF), then transitive dependencies (3NF). |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
Normalise to 3NF — Take a table through 1NF, 2NF, then 3NF by removing repeating groups, then partial dependencies, then transitive dependencies, giving each new table its own key.Removing repeating groups gives 1NFRemove partial dependencies to reach 2NFOrderID -> CustID -> CustName is transitiveOrderItem(OrderID, ProductID, Qty)
PRIMARY KEY (OrderID, ProductID)Customer(CustID, CustName)
Order(OrderID, OrderDate, CustID)