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 | AStudentID: 10452, 10453, 10454 | |
| 2AutoNumber | BThe ID 102 appears twice, so the field is not unique. Each record needs its own ID, such as 103 for the third record. | |
| 3A student ID is a good primary key because no two students share the same ID | CA field type that gives each new record the next unique number automatically, so it can be used as a primary key | |
| 4A name is a poor primary key because two people can share the same name | DName: Sam Nguyen, Sam Nguyen | |
| 5Primary key = FirstName (Jack, Mia, Jack) | EFirstName has a repeated value (Jack twice), so it cannot identify each record. Use a unique field such as StudentID. | |
| 6StudentID: 101, 102, 102, 104 | FA field whose value is different for every record, so each record can be identified |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
primary key — A field whose value is different for every record, such as a student ID or an AutoNumber, so each record can be identified. Names make a poor key because two people can share one.Students: StudentID, Name, Year
Primary key: StudentIDField name: StudentNumber
Data type: AutoNumberA primary key value must be uniqueFields: StudentID, Name, Year
Two students can both be called Sam
Poor primary key: NameThe field that identifies each record
is called the primary key