S6 ICT: database design error rework
- 2026-11-20
S6 ICT: database design error rework
Ten common design misconceptions, each corrected with a one line explanation.
Error rework: ten common slips This paper lists ten common misconceptions: a primary key holding nulls, a foreign key needing uniqueness, 1NF treated as deleting duplicate rows, 2NF limited to single column keys, 3NF removing all redundancy, normalisation always speeding queries, a relationship drawn as a rectangle, many to many stored in one foreign key, a composite key treated as two primary keys, and denormalisation always breaking integrity. Each item names the error and gives the correct rule with one line of explanation.
01 Paper details (check answers afterwards)
| Item | Detail |
|---|---|
| Questions | 10 |
| Suggested time | 25 |
| Difficulty mix | Foundation 3 · Intermediate 3 · Challenge 3 · Error redo 1 |
| Chapter | Chapter: S6 ICT: Database Design and the ER Model |
| Level | Error rework (10 items) |
02 Questions (10 items)
- FoundationA student says a primary key may contain nulls.
- FoundationA student says a foreign key must be unique.
- FoundationA student says 1NF simply means deleting duplicate rows.
- IntermediateA student says 2NF only applies to tables with a single column key.
- IntermediateA student says 3NF removes all redundancy.
- IntermediateA student says normalisation always speeds up queries.
- ChallengeA student draws a relationship as a rectangle in an ER diagram.
- ChallengeA student says a many to many relationship needs only one foreign key.
- ChallengeA student says a composite key is two primary keys.
- Error redoA student says denormalisation always breaks data integrity.
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | A primary key must be unique and not null. | A null row cannot be identified. |
| 2 | A foreign key may repeat, since one teacher can run several courses. | Uniqueness belongs to primary and candidate keys, not to foreign keys. |
| 3 | 1NF requires one atomic value per cell. | Duplicate rows are a key problem, not a 1NF problem. |
| 4 | 2NF targets partial dependency in composite keys. | A single column key cannot produce a partial dependency. |
| 5 | 3NF removes redundancy caused by transitive dependency. | Other redundancy needs BCNF or further design work. |
| 6 | Splitting adds joins, so reads may slow down. | Speed depends on the query pattern and the indexes. |
| 7 | A relationship is a diamond and an entity is a rectangle. | Mixing the shapes makes the diagram unreadable. |
| 8 | Many to many needs a link table holding both primary keys. | One foreign key can only express one to many. |
| 9 | A composite key is one primary key made of two columns. | A table can only have one primary key. |
| 10 | Denormalisation is a trade off, and constraints or triggers can keep the copies consistent. | The risk is real but controllable by design. |
04 What to do after marking
- After marking, redo only the wrong items and write down which step went wrong (formula, unit, or misread number).
- Repeat the same item two days later; move to the next paper only when both attempts are correct.
- Parents only need the answer and note columns; there is no need to explain every item.
Want to draw the flowchart and fill the trace table yourself? Book a TutorZone tutor and unpack all ten items in 25 minutes.Tutor Registration →
Questions and answers are written originally by the TutorZone team and are not taken from any school, publisher or examination authority paper. Every value is checked by computer.



