Edexcel GCSE Computer Science (1CP2) Exam Questions

Award one mark for any of the following up to a maximum of two marks:

• Receives input from/sends output to peripheral devices (1)
• Communicates with/controls a peripheral using its device driver, including installing the driver for a new device (1)
• Manages the print queue/buffer so that print jobs are sent to the printer in turn (1)
• Reports the status of a device/a device error to the user, e.g. out of paper (1)

Allow answers that name a specific peripheral, as long as they also say what the operating system does with it, e.g. 'it controls the printer using its driver'.

Do not accept 'manages peripherals'/'controls the hardware' on its own, as this repeats the question.

Do not accept 'managing files' or 'managing users' (file management and user management are other functions of an operating system).

Award one mark for any of the following up to a maximum of two marks:

• Manages user accounts/profiles/logins (1)
• Authenticates users when they log in (through passwords/biometrics) (1)
• Controls what each user is allowed to access (access rights/permissions) (1)
• Sets which files/folders/resources a user can use (1)
• Gives different levels of access to different users (e.g. administrator/standard user) (1)

Allow 'decides which users can use the computer' for the manage user accounts/logins mark.

Allow references to access to files/folders/resources for the access rights mark, as this is part of user management, not file management.

Do not accept 'manages users' on its own.

Do not accept 'controls user access' on its own, as it is unclear whether this means logging in or access rights.

Do not accept 'manages files' or 'manages peripherals' (these are other operating system functions).

Award up to two marks for a linked description such as:

• Updates/changes the location/path stored for the file (1) so the file can be found in its new folder/location (1)
• Removes the file's entry/reference from the old folder (1) so the file no longer appears/is listed there (1)
• Adds/creates an entry/reference for the file in the new folder (1) so the file appears/is listed in its new location (1)
• Updates the folder/directory listing/structure (1) to show the file's new location/path (1)

Do not accept descriptions of copying the file or leaving a duplicate in the old folder.

Do not accept deleting and recreating the file, or moving the file's data to a different physical location on the disk; the marks are for updating the folder/directory structure.

Award up to two marks for a linked description such as:

• Each user/file is given permissions/access rights (1) so other users cannot read/write/open/change that user's files (1)
• A user may be given read-only/read access to a file (1) so they cannot edit/delete/change it (1)
• Each file is given permissions/access rights for different users (1) so the operating system allows/refuses access depending on which user is logged in (1)
• The operating system checks a user's permissions/access rights when a file is opened (1) so a user with read-only/read access cannot save/delete changes (1)

Do not accept responses about asking for a password/username, as this checks who the user is, not what they are allowed to do.

Do not accept 'files are protected/safe' or 'access rights protect files' without saying how access is limited (e.g. read-only access, permissions for different users).

Indicative content

Administrator accounts

• An administrator account can create new user accounts for new employees and delete accounts when employees leave.
• The administrator can reset a forgotten password, so an employee can get back to work without sharing another person's account.
• The administrator can set the access rights for each user or group, so designers get access to project folders and only directors can open salary files.
• Administrator privileges should be given to only a few trusted employees, as administrators can change any settings on the system.

Standard user accounts

• Designers should use standard user accounts, so they cannot install unauthorised software or change system settings.
• A standard user can be given permission to read and write files in the project folder that their team uses.
• Standard users should not be able to change other users' permissions, so the access rules cannot be removed by accident.
• If a standard user tries to open a file without permission, the operating system denies access.

File permissions

• Each file or folder can have permissions that allow a user to read, write or delete it.
• Project folders can be set so all designers can read and write the files inside them.
• Salary files can be set so only directors can read them, and other users are denied access.
• Permissions can be set for a group of users, such as all designers, which is quicker than setting them for each person.
• A file can be made read-only for standard users, so they can view it but cannot change it.

Levels

• Level 0 (0 marks): No rewardable content.
• Level 1 (1–2 marks): Basic, independent points are made, showing elements of understanding of key concepts/principles of computer science. (AO1) The discussion will contain basic information with little linkage between points made or application to the context. (AO2)
• Level 2 (3–4 marks): Demonstrates adequate understanding of key concepts/principles of computer science. (AO1) The discussion shows some linkages and lines of reasoning with some structure and application to the context. (AO2)
• Level 3 (5–6 marks): Demonstrates comprehensive understanding of key concepts/principles of computer science to support the discussion being presented. (AO1) The discussion is well developed, with sustained lines of reasoning that are coherent and logically structured, and which clearly apply to the context. (AO2)

Level 3 responses must cover administrator accounts, standard user accounts and file permissions, and apply them to the design company.

Do not accept general operating system functions such as managing the processor or memory unless they are explicitly linked to controlling what a user can access.