DP Computer Science Questionbank
A.2 The relational database model
Description
[N/A]Directly related questions
-
19M.2.SL.TZ0.1a:
Construct the entity-relationship diagram (ERD) for this scenario.
-
19M.2.SL.TZ0.3a:
Outline two reasons why databases are normalized.
-
19M.2.SL.TZ0.3b:
Outline why the SALES_PERSON table is not in 1st Normal Form (1NF).
-
19M.2.SL.TZ0.1c:
State the result from the following query:
SELECT Book_Title
FROM BOOK
WHERE Genre = "Non-fiction"
AND ISBN = '0-98124-612-2' -
19M.2.SL.TZ0.1d:
Construct a query to find the titles of the books published by “Orlando Crux”.
-
19M.2.SL.TZ0.2b:
Describe two ways that data security in the school's database can be maintained.
-
19M.2.SL.TZ0.3c:
Construct the 3rd Normal Form (3NF) of the unnormalized relation shown above.
-
19M.2.SL.TZ0.3d:
Outline why it is necessary to ensure that referential integrity is maintained in databases.
-
19M.2.SL.TZ0.3e:
Outline why a primary key may consist of more than one attribute.
-
19M.2.SL.TZ0.1g:
Some data in the MRBS database is redundant.
Outline one problem caused by redundant data.
-
17N.2.SL.TZ0.1c:
Identify two different types of relationships within databases.
- 17N.2.SL.TZ0.2b.ii: State the entity for this example relation.
-
17N.2.SL.TZ0.1d:
Describe the nature of the data dictionary.
- 17N.2.SL.TZ0.2c: Identify an appropriate data type for Student_ID.
-
17N.2.SL.TZ0.3a.i:
State what is meant by redundant data in databases.
- 17N.2.SL.TZ0.2b.i: Define the term entity.
-
17N.2.SL.TZ0.2f.i:
Describe the steps in a query that will output the names of all students who earned the maximum mark on Exam_Two.
-
17N.2.SL.TZ0.3c:
Explain why a compound key is used for the SCHOOL_VOLUNTEERS_TABLE relation.
-
17N.2.SL.TZ0.2f.ii:
Describe the steps in a query that will output the Student_IDs of all candidates who passed.
-
17N.2.SL.TZ0.3b:
Identify three characteristics of the 1st Normal Form (1NF) which are evident in this relation.
-
17N.2.SL.TZ0.3a.ii:
Explain one issue that can be caused by redundant data in a database.
-
17N.2.SL.TZ0.3d:
The following shows the normalized SCHOOL_VOLUNTEERS_TABLE relation:
SCHOOLS_TABLE
Code, School_Name, AddressVOLUNTEERS_TABLE
Code, Date, Num_VolunteersDiscuss whether these relations are in third normal form (3NF).
-
18N.2.SL.TZ0.3d:
Construct the database in the 3rd normal form (3NF) using the notation
Greengrocer (Prod_ID, Prod_Name, Prod_Price, Supp_Name, Supp_Contact, Supp_Phone)You must show all your workings.
You must show all your workings.
-
18N.2.SL.TZ0.2a:
Define the term database management system (DBMS).
-
18N.2.SL.TZ0.3c.i:
Explain the problems that may arise for the following function performed on the given relation. In your answer, you should give an appropriate example: Inserting a new tuple with an item that is supplied by existing supplier.
-
18N.2.SL.TZ0.2b:
Identify three characteristics of logical schema.
-
18N.2.SL.TZ0.2c:
Outline the purpose of a data definition language (DDL).
-
18N.2.SL.TZ0.3a.i:
Identify an appropriate data type for Prod_Price.
-
18N.2.SL.TZ0.3a.ii:
Construct the steps in a query to output the names of all products supplied by Veggy Co. with prices in the range from 4.00 to 10.00 inclusive.
-
18N.2.SL.TZ0.3b:
Outline the redundant data in this relation.
-
18N.2.SL.TZ0.3c.ii:
Explain the problems that may arise for the following function performed on the given relation. In your answer, you should give an appropriate example: Deleting a tuple from the relation.
-
18N.2.SL.TZ0.3c.iii:
Explain the problems that may arise for the following function performed on the given relation. In your answer, you should give an appropriate example: Modifying a specific attribute value in the tuple.
-
19N.2.SL.TZ0.2a:
Construct an entity-relationship-diagram that shows the relationships between the class, order and family.
-
19N.2.SL.TZ0.1a:
Identify one reason why the teacher’s name has been split into two fields.
-
19N.2.SL.TZ0.1f:
The DBA is considering using the email address as the primary key, but is concerned that many of the 250 000 educators who are registering for this online forum may have more than one email address. Users may create duplicate accounts, deliberately or accidently, by using different email addresses as usernames.
Explain the factors that would need to be considered in using a composite primary key instead of only using the email address.
-
19N.2.SL.TZ0.3b:
Outline why data redundancy may be a problem in the LORRY table.
-
19N.2.SL.TZ0.3c:
Identify the steps to create a query to find the names and telephone numbers of the drivers who drive lorries that have more than 60 cubic metres of trailer space.
-
19N.2.SL.TZ0.2f:
Explain, using the example described in the scenario, why referential integrity is important in databases.
-
19N.2.SL.TZ0.2d:
Identify two characteristics of a conceptual schema.
-
19N.2.SL.TZ0.2e:
Explain why the use of data modelling is critical to the success of a database, such as the one used in this scenario.
-
19N.2.SL.TZ0.3a:
Identify two characteristics that make a database unnormalized.
-
19N.2.SL.TZ0.3d:
Normalize the database to 3NF. Use the same format as shown, ensuring that primary keys are clearly indicated by underlining them.
-
20N.2.SL.TZ0.1d:
Outline two issues caused by storing redundant data.
-
20N.2.SL.TZ0.3c.ii:
Outline why the inclusion of a derived field will not affect the normalization of a database.
-
20N.2.SL.TZ0.1a:
Construct the entity-relationship diagram (ERD) that shows the relationship between the individual, their driving license, and their vehicle(s).
-
20N.2.SL.TZ0.2d:
Explain how the Billetmania database management system ensures that a seat is not booked by two people simultaneously.
-
20N.2.SL.TZ0.3a:
Define the term record.
-
20N.2.SL.TZ0.3b:
Identify the steps to create a query to find the vineyards and names of fruity wines where the quantity in stock is between 25 and 35 bottles.
-
20N.2.SL.TZ0.3c.i:
Identify the steps to create a non-persistent derived field called
TotalPrice
, which would hold the total value of wine stored for each record. -
20N.2.SL.TZ0.3d:
Construct the 3rd Normal Form (3NF) of the unnormalized Wine file.
-
20N.2.SL.TZ0.3e:
Outline why a single-field primary key is not always an appropriate solution for normalized databases.
-
18M.2.SL.TZ0.1c:
Identify the steps to create a query to find the names of customers whose account balance is greater than $300 000.
-
18M.2.SL.TZ0.1d:
Explain how controlling access rights contributes to the security of the Galaxy Bank database.
-
18M.2.SL.TZ0.3c:
Outline what would be necessary to make the above unnormalized table conform to 1st Normal Form (1NF).
-
18M.2.SL.TZ0.3d:
Construct the 3rd Normal Form (3NF) of the unnormalized relation shown above.
-
18M.2.SL.TZ0.1e:
Explain how row locking ensures the consistency of the data in the Galaxy Bank database.
-
18M.2.SL.TZ0.3a:
Explain one benefit of normalizing a database.
-
18M.2.SL.TZ0.1a:
Construct the entity relationship diagram (ERD) that shows the relationship between the bank branch, the customers and their loans.
-
18M.2.SL.TZ0.1b:
With reference to the table LOANS, state the output of the following query:
SELECT LOANS.Loan_ID, LOANS.Customer_ID, LOANS.Amount, LOANS.Type
FROM LOANS
WHERE (LOANS.Amount > 600000) AND ((LOANS.Type = "Home") OR
(LOANS.Type = "Venture")); -
18M.2.SL.TZ0.3e:
Explain the difference between 2nd Normal Form (2NF) and 3rd Normal Form (3NF).