Question 1
9 marks
1 9 marks
Rosa has recently opened a new leisure centre. Currently she has 150 members, however, she is estimating that this will increase to around 10 000 members.
Rosa will store members' details in a database. She will also store gym class bookings and appointments with fitness instructors.
Rosa is considering using either a flat file database or a relational database.
Discuss the benefits and drawbacks of flat file databases and relational databases and which one would be the most suitable for Rosa.
You should include the following in your answer:
- the features of flat file databases and relational databases
- the benefits and drawbacks of each type of database
- which type of database would be the most suitable for Rosa.
Mark scheme 1
Tick each point your answer makes. Your mark is worked out from your ticks, and you can change it.
Mark Band 3-High Level (7-9 marks)
The candidate demonstrates a thorough knowledge and understanding of databases. The material is generally accurate and detailed.
The candidate is able to apply their knowledge and
understanding directly and consistently to the context provided. Evidence/examples will be explicitly relevant to the explanation.
There is a well-developed line of reasoning which is clear and logically structured. The information presented is relevant and substantiated.
A mark band 3 answer will cover benefits and disadvantages of both flat file and relational databases. The expansions will relate to Rosa’s needs and will go on to evaluate why a relational database is most appropriate.
Mark Band 2-Mid Level (4-6 marks)
The candidate demonstrates reasonable knowledge and understanding of databases; the material is generally accurate but at times underdeveloped.
The candidate is able to apply their knowledge and
understanding directly to the context provided although one
or two opportunities are missed. Evidence/examples are for the most part implicitly relevant to the explanation.
There is a line of reasoning presented with some structure. The information presented is in the most part relevant and supported by some evidence.
A mark band 2 answer will cover features of both flat file and relational databases and will expand the points, relating these to benefits and drawbacks and size of Rosa’s data set although these may not be balanced. There will be an attempt to recommend which type is suitable.
Mark Band 1-Low Level (1-3 marks)
The candidate demonstrates a basic knowledge of databases; the material is basic and contains some inaccuracies. The candidate makes a limited attempt to apply acquired knowledge and understanding to the context provided.
The candidate provides nothing more than an unsupported assertion.
The information is basic and communicated in an
unstructured way. The information is supported by limited evidence and the relationship to the evidence may not be clear.
A mark band 1 answer will contain some basic, relevant points related to features of flat file and/or relational databases. It may not be linked to Rosa’s specific needs.
0 mark
No attempt to answer the question or response is not worthy of credit.
Guidance
Points may include but aren’t limited to:
AO1 Knowledge and Understanding
A flat file database stores data in a single table, often in a plain text file. Usually, each line will hold a single record and delimiters such as commas are used to separate this into different fields.
Benefits:
- They are easy to set up as only one table is needed
- All records are stored in one place
Drawbacks:
- Tables can contain lots of redundant data which increases the amount of storage space needed
- Searching the database can be slower as there is more data to search
- The database can be more difficult to manage and possibly expand in the future
A relational database stores data in multiple different tables. These are linked together using relationships created by primary and foreign keys.
Benefits:
- There is less duplication of information so less redundant data which can reduce the file size
- The database is easier to manage and easier to expand in the future
- Searching the database may be faster as there is less data / not all tables need to be searched
- It can be more secure as different tables means different people could have different access
Drawbacks:
- They are generally more difficult to set up and need more technical knowledge to do things like normalisation.
- Data is spread out between multiple tables. Some tables may be link tables which only display key fields / references
- They are more expensive as you will need a DBMS rather than just a basic file
AO2 Application
- Given that Rosa currently has 150 members, a flat file database will be suitable
- However, as the business expands, using a flat file database may prove problematic
- She could end up with a lot of redundant data as each time a new booking/appointment is made, it may store repeated data.
- The more data Rosa has, the more likely there could be inconsistencies if data is edited/updated and her data would lose integrity
- A relational database would be more efficient.
- Membership details can be stored once and then their membership ID number can then be used to make a booking
- A relational database will also allow her to expand even further in the future as additional tables can be added. However, the database will need to be normalised to ensure data is consistent, in the same format and that dependencies are reduced
AO3 Evaluation
The most suitable database for Rosa would be a relational database. Although this is more complex and the data needs to be normalised, it will store less repeated data when her company expands. It will also allow the database to be easily maintained and expanded in the future and will be easier to keep data secure, which is important.
Examiner’s Comments
There were some really good responses to this question. More successful candidates were able to explain the features of both types of database as well as giving relevant benefits and drawbacks of each which they then applied to the scenario well and gave a recommendation. Some candidates gave good descriptions of the features of each type but were unable to apply their knowledge to
the scenario other than saying the membership was going to increase. There were a number of candidates who confused a database with a table stating that a relational database was a number of related databases and not a number of related tables.
[An examiner's marking symbol, not shown here.]
Misconception
The main misconception was to confuse database with table although some candidates also confused the different keys used in a relational database and what they were used for.
Exemplar 3
[Image redrawn from the original mark scheme by an AI model (Gemma 4 12B). It may contain mistakes.]
A candidate's handwritten answer:
A flat file database is a type of database that only contains one table. This means that all data is stored in "tables", headed by "headers" and fields. It doesn't require a primary key or to be normalised. A relational database uses multiple tables linked together using foreign keys, which could create a many relationship between different tables in the database.
A flat file database has many advantages. Firstly, it is relatively simple & easy to understand. This is because all records are stored in tables, so all the information is in one place. However, there are drawbacks. If it is a large number - e.g. both multiple cities and approximately, extra records would be wanted. This would lead to a large amount of redundant data being included such as a number [unclear] appearing twice. This would increase the amount of space the database takes up. In other words, it would be difficult to search the database.
A relational database also has many benefits. When a relational database has been normalised, it becomes very efficient & search and easier to use. It will do so well as through the process of normalisation, large amounts of redundant data would be deleted, reducing the [unclear] space "saved" for
[unclear] the database. For example, by storing "cities" for approximately [unclear] number for "country", and "cities" for "country details", the membership details [unclear] could be written and again [unclear] for approximately [unclear] "country", saving [unclear] space.
Overall, a relational database would be much more suitable for large databases. A flat file database is [unclear] for [unclear] e.g. with 100 records, if the first 10,000 records in the [unclear] online [unclear] will be [unclear] difficult to locate specific records when searching, as there would be far too much redundant data, [unclear], and the file size would be [unclear] large if extra details are included each time an appointment is made. However, if [unclear] want to use a relational database, there would be much less redundant data, [unclear] [unclear] for the file size and [unclear] [unclear] for each record, as [unclear] [unclear] [unclear] will be used in a relational database. [unclear] [unclear] [unclear] [unclear] will be used in a relational database. [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [unclear] [
The candidate has shown good application to the scenario as well as benefits and drawbacks of both database types. They have made a valid
recommendation which is justified.