U2 Database Design Quiz - Part A

What is the significance of normalisation in database design?

• Normalisation helps to minimise data duplication and enables data integrity.

• It increases redundancy in the database.

• It reduces the number of tables needed.

• It automatically creates relationships between tables.

What is the recommended first step before creating tables in a database?

• Design your tables in Word first.

• Start entering data directly into the database.

• Write SQL code before planning structure.

• Create forms before defining tables.

What is a composite key in database design?

• A composite key is composed of multiple fields and should be unique to meet the requirement of a Primary key.

• A composite key is a field that always auto-increments.

• A composite key is used to link unrelated tables.

• A composite key must contain only numeric values.

When designing relationships, what type is most commonly used?

• One-to-many relationship.

• Many-to-many without a linking table.

• Circular relationships between three tables.

• One-to-one relationships only.

When would you use a one-to-one relationship?

• When each record in Table A relates to only one record in Table B and vice versa.

• When you want to link one record to many others.

• When multiple records share the same key.

• When linking unrelated tables.

What file format should you use to save your relationship screenshot?

• PDF using ‘Microsoft Print to PDF’, named activity1.

• JPEG saved in Paint.

• Word document with image pasted.

• Screenshot saved as a .txt file.

What is a better way to ensure a presence check than just setting 'Required' to 'Yes'?

• Use 'Validation Rule' = 'Is not null' with a helpful 'Validation Text' message.

• Leave the field blank by default.

• Use a default value instead.

• Make the field optional but use conditional formatting.

What is the purpose of a table lookup?

• To look up Foreign Keys and present values in a dropdown list.

• To store all related records in one field.

• To filter data automatically.

• To sort records by default.

What settings should be changed in a lookup field to prevent invalid input?

• Set 'Limit to List' = Yes, 'Allow value list edits' = No, 'Allow multiple values' = No.

• Enable multiple selections for flexibility.

• Set Limit to List = No for open-ended input.

• Allow users to edit the list for convenience.

When are value lookups suitable?

• For short, fixed lists like days of the week or Gold, Silver, Bronze, etc.

• For storing customer names and addresses.

• For referencing external database keys.

• For dynamic values that change frequently.