A database stores organised, related information so it can be efficiently retrieved and updated. Data is organised into tables, similar to a spreadsheet: each table has fields (columns, like "Name" or "Email") and records (rows, each representing one entry, like one customer). A key field (like a unique ID) helps identify each record uniquely, especially when tables need to be linked together.
Example
A school's student database might have a table called "Students" with fields for StudentID, FirstName, LastName and YearLevel. Each row (record) represents one student — StudentID 054 might be the record for a student named Joe in Year 9.
Key terms
Table:
A structured collection of related data, organised in rows and columns.
Field:
A single column in a table representing one type of data.
Record:
A single row in a table, representing one complete entry.
Questions
1. A database stores:
Organised, related information
Only images
Nothing useful
Only passwords
2. A table organises data into:
Rows and columns
A single list with no structure
Only images
Sound files only
3. A field is:
A single column representing one type of data
An entire table
A whole database
A type of password
4. A record is:
A single row representing one complete entry
An entire table
A single field only
A type of software
5. In a "Students" table, StudentID, FirstName and YearLevel would each be a:
Field
Record
Database
Password
6. One row representing one specific student is called a:
Record
Field
Table name
Database name
7. A key field is used to:
Uniquely identify each record
Delete all records
Store images only
Slow down the database
8. Why is a unique key field (like StudentID) useful, rather than relying on names alone?
Two people could share the same name, but IDs are guaranteed unique
Names are always unique with no exceptions
Key fields have no real purpose
IDs are less reliable than names
9. A "Products" table in a shop's database would likely include a field for:
Product price
A random unrelated topic
Student year level
A type of malware
10. If a school has 500 students, its Students table would have approximately how many records?
500
5
50
5,000
11. A database allows information to be:
Efficiently retrieved and updated
Never changed once entered
Only viewed, never searched
Randomly scrambled
12. Searching a database for "all students in Year 9" would filter based on the:
YearLevel field
StudentID field only
The entire database randomly
No specific field
13. A relational database can link multiple tables together using:
Shared key fields
Random guessing
Colour coding only
No connection method at all
14. Compared to a simple paper list, a digital database's main advantage is:
Being able to quickly search, sort and update large amounts of data
Being slower to search through
Having no way to organise information
Only working for very small amounts of data
15. A library database linking a "Books" table and a "Borrowers" table would likely use a shared field like:
A BorrowerID to connect which borrower has which book
The book's cover colour
No connection is needed between tables
The library's opening hours
16. Why might splitting information into multiple related tables (rather than one giant table) be good database design?
It reduces repeated data and makes updates more efficient and consistent
One giant table is always more efficient
Splitting tables always causes data loss
Database design has no impact on efficiency
17. A database query like "find all orders over $100 from the last month" relies on the database's ability to:
Filter and search records based on multiple conditions
Only display every record with no filtering
Delete unrelated records automatically
Only work with one condition at a time, ever
18. Why is data validation (checking that entered data is in the correct format) important in database design?
It helps prevent errors and inconsistent or unusable data from being stored
Validation always makes databases slower with no benefit
Databases never need any data checks
Validation removes the need for fields entirely
19. A hospital database storing patient records would need strong security measures mainly because:
The data is highly sensitive and its misuse could seriously harm patients' privacy
Hospital databases contain no sensitive information
Security is irrelevant for medical data
Patient data is always public information
20. Why might duplicate records (the same customer entered twice with slightly different details) cause problems in a database?
It can lead to inconsistent, unreliable information and wasted storage
Duplicates always improve database accuracy
Duplicate records have no negative effects
Databases automatically prevent all duplicates with no design effort
21. A database backup is important mainly because it:
Provides a way to recover data if the original is lost, corrupted or deleted
Makes the original database permanently unusable
Has no practical benefit for real organisations
Is only relevant for very small databases
Answer key (parent copy)
1. Organised, related information
2. Rows and columns
3. A single column representing one type of data
4. A single row representing one complete entry
5. Field
6. Record
7. Uniquely identify each record
8. Two people could share the same name, but IDs are guaranteed unique
9. Product price
10. 500
11. Efficiently retrieved and updated
12. YearLevel field
13. Shared key fields
14. Being able to quickly search, sort and update large amounts of data
15. A BorrowerID to connect which borrower has which book
16. It reduces repeated data and makes updates more efficient and consistent
17. Filter and search records based on multiple conditions
18. It helps prevent errors and inconsistent or unusable data from being stored
19. The data is highly sensitive and its misuse could seriously harm patients' privacy
20. It can lead to inconsistent, unreliable information and wasted storage
21. Provides a way to recover data if the original is lost, corrupted or deleted