NEW
Font size
WorksheetsUnit 2 question bank
Total questions: 70
Worksheet time: 35mins
In a college student management system, what must a Distinction-level Relationships diagram in Access show in the Relationships window?
All entities with enforced referential integrity and correctly typed 1–many joins
Some related tables linked by matching field names
Only primary keys with no foreign keys shown
A single table with all attributes combined
For Distinction, how should a many-to-many relationship between Students and Modules be implemented in Access?
Via a junction table (e.g. Enrolments) with composite FK fields and enforced referential integrity
By adding a multi-value field to the Students table
By duplicating module columns in the Students table
By creating a calculated field that concatenates student and module IDs
Which change most strongly evidences full normalisation (no redundancy) for Distinction in the Relationships window?
Moving tutor contact details from Modules to a separate Tutors table linked by TutorID
Adding a lookup field for module names inside Students
Copying student emails into every related table to speed up reports
Storing both TutorName and TutorID in every child table
In Access, which action confirms correct 1–many relationships for Distinction-level ERD?
Enforce Referential Integrity
Create a new table
Set a primary key
Delete duplicate records
A student sets StudentID (Short Text) in Students and StudentID (Number) in Enrolments. For Distinction, what must be corrected?
Match the data types and field sizes for PK/FK pairs across tables
Rename the fields to identical names only
Change both fields to AutoNumber in both tables
Permit nulls in foreign keys to avoid join failures
Which description best matches a Distinction-level ERD outcome?
All tables fully normalised (3NF), no repeating groups, and all relationship types accurately shown
A partially normalised set with minimal duplication allowed for convenience
A single wide table to avoid complex joins in forms
Two tables with many lookups and no enforced links
In Table Design View, which combination aligns with Distinction-level field design for Dates of Birth in Students?
Data Type: Date/Time; Required: Yes; Validation Rule: <=Date(); Validation Text explaining future dates are not allowed
Data Type: Short Text; Required: No; no validation
Data Type: Date/Time; Required: No; Allow Zero Length: Yes
Data Type: Number; Input Mask applied for DD/MM/YYYY
For Distinction, how should a Grade field (A–F only) be validated in Access?
Use a Validation Rule: In("A","B","C","D","E","F") with clear Validation Text
Use a Short Text field with no validation (teacher checks later)
Use a Number field with an Input Mask
Store grades as free-text notes in a memo field
Which naming approach best meets Distinction-level consistency for tables and fields?
tblStudents/StudentID, tblModules/ModuleID, tblEnrolments/EnrolmentID
STUDENTS/ID, MODULES/ID, LINKS/ID
Table1/Field1, Table2/Field2
StudentsTable/PrimaryKey
What is required of PK/FK data types at Distinction level in Access?
PKs and their corresponding FKs must use the same data type and compatible field size
PKs must be AutoNumber and FKs must be Short Text
PKs may vary; Access will coerce during joins automatically
FKS should be optional text fields to prevent errors
For Distinction, how should you prevent negative attendance values in a Number field?
Validation Rule: >=0 and appropriate Validation Text
Use an Input Mask only
Store attendance as Short Text and check manually
Set Default Value to 0 without validation
In the Property Sheet, which setting supports Distinction-level data quality for a Postcode field?
Validation Rule
Input Mask
Default Value
Required
A report must summarise attendance by module. For Distinction, which approach is best in Access?
Create a totals query grouped by ModuleID and bind a grouped report with clear headers and a grand total
Export to Excel to calculate totals and paste back
Add a calculated control directly to a blank report with no query
Build a crosstab without grouping then filter manually
For Distinction, a query to list students who have not submitted an assignment by a due date should use which criterion?
SubmissionDate Is Null OR SubmissionDate > [Enter Due Date]
SubmissionDate < [Enter Due Date]
SubmissionDate = ""
SubmissionDate Like "*"
Which calculated field best fits Distinction-level accuracy in a query for final marks?
FinalMark: ([ExamMark]*0.6)+([CourseworkMark]*0.4) with data types ensured numeric
FinalMark: [ExamMark]+[CourseworkMark]
FinalMark: CStr([ExamMark]) & CStr([CourseworkMark])
FinalMark computed in the form only, not the query
16. For Distinction, fields for a report presented to faculty should be selected by:
Including only relevant and significant data.
Selecting all available fields regardless of relevance.
Choosing fields based on personal preference.
Randomly picking fields without criteria.
Which design choice most supports Distinction-level readability in Report Layout View?
Use grouping, page headers, calculated totals, and consistent alignment/format
Random font sizes and colours to highlight values
Single-column layout with no grouping and no totals
Rely on default auto-generated report with no edits
A parameter query prompts for Module Code. For Distinction, which prompt practice is best?
Use square brackets with a clear prompt (e.g. [Enter Module Code]) and validate inputs
Use ambiguous prompts to allow flexible entry
Rely on form filters only
Type the module code directly into SQL view
For Distinction-level structure testing, which test set is most appropriate for the Students table?
Normal (valid), Erroneous (invalid), and Extreme (boundary) test data with expected results specified
Only normal data because users should enter valid values
Only extreme data to stress-test the system
Erroneous data only to trigger error messages
Which evidence best proves Distinction-level structural robustness?
A completed test plan table showing test data, expected vs actual results, and fixes applied
A verbal statement that 'it works'
A screenshot of one successful data entry
A printout of table design only
During testing, a FK allows a value not present in the parent table. For Distinction, what should you evidence?
Relationship updated to enforce referential integrity and re-tested with results recorded
A note explaining this is acceptable for speed
Change the FK to Short Text to allow any value
Remove the relationship to avoid errors
Which documentation detail aligns with Distinction-level structure testing?
Specific expected results tied to each identified test input, not generic statements
Generic expected results such as 'should work'
No expected results; only actual outcomes
Only screenshots without descriptions
A boundary test for a mark field (0–100) at Distinction level should include which inputs?
–1, 0, 100, 101 with clear expected outcomes and validation messages
10, 50, 90 only
100 only because it is the maximum
Any random number
Which explanation best exemplifies Distinction-level evaluation of structure?
A fully supported justification of 3NF design choices linked to the college scenario (e.g. separation of Tutors, Modules, Rooms)
A list of tables only
A description of how to open Access
An opinion that '3NF is always best' with no evidence
What language style supports Distinction in evaluation?
Fluent and accurate technical vocabulary (e.g. 1–many, junction table, surrogate key, referential integrity)
Casual language with minimal terminology
Acronyms without definitions
No technical vocabulary to keep it simple
Which link most clearly ties the solution to scenario requirements for Distinction?
Explaining how enrolment rules enforce one student in many modules via Enrolments with referential integrity
Saying 'It meets requirements' without detail
Showing a screenshot of the Navigation Pane
Referencing a different project's needs
Which metric strengthens a Distinction-level justification of structure?
Explaining how normalisation reduces update anomalies and improves query performance in Access
Counting total number of tables only
Stating that forms look neat
Saying 'performance is fine' without evidence
Which feature set aligns with Distinction-level user interface in Access for admin staff?
Navigation Form, well-labelled command buttons, tab order set, consistent formatting and themes
Unlinked forms opened manually from the Objects list
Single form with all fields from all tables
Relying on datasheet view for data entry
For Distinction, which control setup on a Student Entry form best minimises errors?
Combo boxes for FK selections, input masks for dates/postcodes, and required fields with validation text
Text boxes for all fields with no validation
Allow all fields to be optional
Use continuous forms only
Which Access tool best evidences automation for Distinction?
Macros or VBA event procedures (e.g. Before Update) to validate and handle unexpected events
Manual checks performed by the user
Default values only
Navigation Pane grouping
A button 'Generate Attendance Report' is required. For Distinction, what is the best implementation?
A macro attached to the button to open a grouped report based on a prebuilt totals query
A label explaining where to find reports manually
A hyperlink to an external spreadsheet
A command button with no action
Which layout choice supports Distinction-level usability in Form Design View?
Consistent alignment, logical tab order, grouped related fields, and descriptive control tips
Random placement of controls for speed
Rely on default auto-generated layout
Use colours heavily to decorate forms
For Distinction, how should unexpected events be handled on data entry?
Use error-handling macros/VBA with user-friendly messages and rollback of invalid operations
Let Access show default error numbers
Ignore errors and ask users to retry
Disable validation to prevent messages
Which statement best evidences 'fully meets the given criteria' for Distinction?
All functional requirements implemented and verified via successful tests across all forms/reports
Most features implemented but some untested
Basic CRUD only
Interface opens but some buttons do nothing
Which check supports 'easy maintenance by a third party' at Distinction level?
Consistent object naming (forms/reports/queries), comments in macros/VBA, and a simple navigation structure
Hide objects and use ad-hoc names
Store logic in many hidden macros
Use duplicate object names for speed
Which test evidence proves Distinction-level interface testing for the Enrolments form?
A table of test cases with screenshots, expected vs actual results, and notes on fixes applied
One screenshot of a successful save
A test note saying 'form OK'
A list of field names only
In testing, a combo box allows selecting a non-existent ModuleID. For Distinction, what should be done?
Rebuild the Row Source to the Modules table and re-enforce referential integrity; re-test and record results
Allow any text to be typed and trust users
Remove the combo box and allow free entry
Ignore; it happens rarely
Which set qualifies as normal/erroneous/extreme test data for a Date of Birth field?
Valid: 10/10/2005; Erroneous: 'abcd'; Extreme: 31/12/1899 and Tomorrow's date
Valid: any text; Erroneous: any number; Extreme: any symbol
Valid: 01; Erroneous: 02; Extreme: 03
Only today's date values
What distinguishes Distinction-level expected results in interface testing?
They are specific to the exact input and include the intended validation message or outcome
They are generic statements like 'should save'
They are omitted to save time
They are written after testing is complete
Which follow-up action is required after fixing a defect for Distinction-level evidence?
Re-test the exact case and record the new actual result referencing the fix
Delete the test case
Mark the case as 'N/A' without re-test
Assume similar cases are fixed
Which evaluation statement best matches Distinction-level usability analysis?
The interface is intuitive: Navigation Form groups tasks logically; tab order supports efficient entry; labels/tooltips aid novice users
The interface opens quickly without errors
The colours are bright and engaging
There are many forms available
For Distinction, how should performance be justified in the evaluation?
Explain how indexes on StudentID/ModuleID and filtered queries reduce load times for forms and reports
Say 'performance is fine'
Add more memory to the PC
Create larger tables to improve speed
Which technical vocabulary demonstrates Distinction-level evaluation?
Terms like 'referential integrity', 'junction table', 'Before Update event', 'totals query', 'cascading update'
General words like 'thing', 'stuff', 'nice'
Acronyms only with no context
No terminology to keep it simple
Which linkage to scenario requirements best supports Distinction-level evaluation?
Explaining how attendance reports by module support Heads of Department decision-making
Saying 'reports are useful'
Referencing a different school's needs
Stating 'we have reports' without purpose
Which improvement suggestion fits Distinction-level evaluation style?
Propose specific enhancements (e.g. add a macro to prevent duplicate enrolments) with justification
Suggest 'make it look better'
Add more colours to forms
No improvements needed
In Access, which Relationships window setting evidences Distinction-level integrity?
Enforce Referential Integrity (and cascade updates if appropriate)
No enforcement to avoid errors
Use text keys everywhere
Allow orphan records
For Distinction, how is a many-to-many Students–Modules link represented?
Through a junction table (Enrolments) with two foreign keys
Direct many-to-many join line only
By duplicating module fields in Students
By storing module names in a multi-value field
Which Table Design View setting prevents future Date of Birth entries at Distinction level?
Validation Rule: <=Date() with explanatory Validation Text
Required: No
Input Mask only
Data Type: Short Text
Which naming scheme aligns with Distinction?
tblStudents.StudentID; tblModules.ModuleID; tblEnrolments.EnrolmentID
STUDENTS.ID; MODULES.ID
Table1.Field1
MainTable.PrimaryKey
Which criterion finds overdue submissions for Distinction?
SubmissionDate Is Null OR SubmissionDate > [Enter Due Date]
SubmissionDate Like "*"
SubmissionDate = 0
SubmissionDate < Date() only
Which is a Distinction-level calculated field?
FinalMark: ([ExamMark]*0.6)+([CourseworkMark]*0.4)
FinalMark: [ExamMark]+[CourseworkMark] only
Final: CStr([ExamMark]) & [CourseworkMark]
Mark: [ExamMark]*[CourseworkMark]
7. Which report practice supports Distinction readability?
Using clear headings and subheadings
Including excessive jargon
Using long, complex sentences
Omitting visual aids
Best evidence for Distinction structure testing?
Test plan with normal/erroneous/extreme data and expected vs actual results
One successful data entry
Only extreme tests
Only screenshots
What must match for PK/FK pairs at Distinction level?
Data types and field sizes
Field captions only
Number formats only
Nothing; Access coerces automatically
How should invalid attendance be prevented?
Validation Rule: >=0 with clear Validation Text
Manual checks later
Text data type
Default only
Which tool adds automation to achieve Distinction?
Macros or VBA event procedures (e.g. Before Update)
Manual instructions
Which interface evidence shows Distinction?
Navigation Form, labelled buttons, logical tab order, consistent formatting
Datasheet view only
Random button placement
Unlinked objects
Distinction-level testing of a form requires which?
Specific expected results per input and screenshots of outcomes
Generic expectations only
No expected results
Notes after testing only
What evaluation language fits Distinction?
Fluent technical vocabulary linked to scenario
Casual tone, no terms
Acronyms only
No terminology
Which improvement is Distinction-appropriate?
Add macro to prevent duplicate enrolments; justify with scenario needs
Change colours
Delete validation
Hide forms
Which indexing decision helps Distinction-level performance?
Index StudentID and ModuleID used in joins/filters
Index all fields
No indexes
Index only text description fields
Where is the Validation Rule applied for a field in Access?
In the Property Sheet for the field (Table Design View)
In the Navigation Pane
In the Relationships window only
In Report Layout View
Which join type usually represents parent-to-child at Distinction?
One-to-many with enforced referential integrity
Many-to-many direct link
One-to-one everywhere
No joins
Which prompt style is Distinction-appropriate in parameter queries?
Clear bracketed prompts (e.g. [Enter Module Code])
Ambiguous prompts
No prompts; rely on guessing
Hard-code the value
Which practice improves maintainability for Distinction?
Regular code reviews
Ignoring documentation
Frequent code duplication
Lack of version control
Which test inputs demonstrate boundary analysis for 0–100 marks?
–1, 0, 100, 101
10, 50, 90 only
0 only
Any random number
Which control type minimises FK entry errors?
Combo box bound to FK with Row Source from parent table
Text box free entry
Label
Hyperlink
Which report field selection suits Distinction?
Only relevant fields, remove redundant columns
All fields, just in case
Keys only
Screenshots instead of fields
Which macro action aligns with Distinction error handling?
Display custom message and cancel update on invalid input (Before Update)
Let default error show
Which final evidence validates 'fully meets criteria' at Distinction?
All requirements tested successfully with results captured in the test plan
Most requirements attempted
Basic CRUD only
Draft UI without tests
