Grade 12 Theory III — Relational Database Design & Normalisation

Question 1

The process of analysing raw source documents (like a till slip) to identify the data entities a database should contain is part of:

Question 2

The overall purpose of normalisation is to:

Question 3

A system specifically designed to record and process individual database transactions (e.g. a sale, a booking) is called a:

Question 4

A key field made up of MORE than one field combined together, used to uniquely identify a record, is called a:

Question 5

A field that could have served as the primary key, but wasn't chosen, is referred to as a/an:

Question 6

Which of the following is a core characteristic of a well-designed relational database, alongside data integrity and security?

Question 7

Why is data maintenance EASE considered a characteristic of a good database design?

Question 8

When setting up a one-to-many (1:M) relationship between two tables, the foreign key is normally placed in:

Question 9

Which of these correctly describes querying a database using a JOIN across two tables?

Question 10

Which of these situations is a classic sign of an UN-normalised database, likely to cause anomalies?

Question 11

Splitting one large, redundant table into several smaller, related tables — connected via key fields — is the practical outcome of:

Question 12

Reinforcing data integrity in a relational database design specifically means ensuring:

Question 13 — Match the columns

Match each database design term in Column A to its description in Column B.

Question 14 — Match the columns

Match each characteristic of a good database in Column A to what it guarantees in Column B.

Question 15

In database design, a real-world object or concept that data is stored about — e.g. a Customer or a Product — is called a(n):

Question 16

A specific piece of data describing an entity — e.g. a Customer's Surname — is called a(n):

Question 17

Ensuring that a foreign key value always matches an existing primary key value in the related table is called:

Question 18

A many-to-many relationship between two tables is typically resolved during design by introducing a:

Question 19

When designing a relational database, which of these generally comes FIRST, before assigning keys and relationships?

Question 20

Why does 'record organisation' — giving each table a well-defined, appropriately-scoped set of related fields — matter early in database design?