S6 ICT: database design basics
- 2026-11-20
S6 ICT: database design basics
Start from degree and cardinality, then check primary keys, foreign keys, ER shapes and superkey counts.
Basics: relations, keys and ER diagrams This paper works from three tables: STUDENT with 4 columns and 8 rows, COURSE with 12 courses run by 5 teachers, and ENROL with 22 enrolments. It separates degree from cardinality, then checks the unique not null rule for primary keys, foreign key targets, the three ER shapes and an average of 2.4 courses per teacher. The later items count 4 superkeys and explain when a composite key is unavoidable, and the last item corrects the claim that a primary key may hold nulls.
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 | Basics (10 items) |
02 Questions (10 items)
- FoundationThe STUDENT relation has 4 columns (StudentID, Name, Class, Email) and 8 rows. What is its degree?
- FoundationWhat is the cardinality of the same relation?
- FoundationWhich two conditions must a primary key satisfy?
- IntermediateStudentID in ENROL(StudentID, CourseID) is a foreign key. Which primary key does it reference?
- IntermediateWhich shapes mark an entity, an attribute and a relationship in an ER diagram?
- Intermediate5 teachers run 12 courses. What is the average number of courses per teacher?
- ChallengeIn R(A, B, C), A is a unique key. How many superkeys does R have?
- ChallengeWhen is a composite key required?
- Challenge22 enrolments are spread over 12 courses and 8 students. What are the averages per course and per student?
- Error redoA student claims a primary key may contain nulls. Where is the error?
03 Answers and one-line notes
| # | Answer | One-line note |
|---|---|---|
| 1 | The degree is 4. | Degree counts columns, not rows. |
| 2 | The cardinality is 8. | Cardinality counts the rows stored in the table today. |
| 3 | The value is unique for every row and never null. | Uniqueness prevents duplicates and the no-null rule keeps every row identifiable. |
| 4 | It references StudentID in STUDENT. | A foreign key points at another relation primary key and keeps referential integrity. |
| 5 | Rectangle for an entity, oval for an attribute and diamond for a relationship. | Each shape has one job, so mixing them makes the diagram unreadable. |
| 6 | The average is 2.4 courses. | 12 divided by 5 is 2.4, and an average does not mean every teacher runs the same number. |
| 7 | There are 4 superkeys. | Every superkey must contain A while the other two columns are optional, so the count is 2 to the power of 2. |
| 8 | When no single column can identify a row on its own. | In ENROL only StudentID together with CourseID is unique, because either column alone repeats. |
| 9 | 1.83 per course and 2.75 per student. | 22 divided by 12 is 1.83, and 22 divided by 8 is 2.75. |
| 10 | A primary key must be unique and not null, since a null identifies no row. | If nulls were allowed, several null rows would collide and uniqueness would collapse. |
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.



