Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1PRIMARY KEY (studentId) | AAn ID field that must always hold a value, so no record can have a blank key | |
| 2studentId INTEGER NOT NULL | BLast names can be shared by different students, so they are not unique. Use an ID number instead. | |
| 3Two students can share a first name or date of birth, so these fields are unsuitable as a primary key | CChooses studentId as the field that identifies each record, because its values are unique and never blank | |
| 4When no field is unique, add a new ID field to the table and use it as the primary key | DALTER TABLE Pets ADD petId INTEGER | |
| 5PRIMARY KEY (house) | EfirstName, dateOfBirth | |
| 6PRIMARY KEY (lastName) | FThe house field has repeated values such as Red and Blue, so it cannot identify one record. Use a unique field such as studentId. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
PRIMARY KEY — The field chosen to identify each record. Its values must be unique and never blank, like an ID number. Names and dates of birth can repeat, so they are unsuitable.Student(StudentID, Name, DOB, Form)
Primary key: StudentIDCREATE TABLE Student (
StudentID INTEGER PRIMARY KEY,
Name TEXT);Can DOB be the primary key? No
Two pupils can share a date of birth.Pet(Name, Breed, Age)
No unique field, so add a new field: PetIDKey values must be unique and never blank