Edexcel GCSE Computer Science (1CP2) Exam Questions

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

• Decides which process is given use of the CPU (1) so that more than one program can run/appear to run at the same time (1)
• Allocates CPU time to each process (1) so that no single process takes control of the CPU (1)
• Manages the states/life-cycle of each process (1) so processes can be moved between ready/running/blocked (1)
• Keeps track of the processes and their status (1) so a process waiting for a resource can be returned to the CPU when it is ready (1)

Do not accept responses that only describe what a process is.

Do not accept responses that only list the types of operating system management.

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

• Allocates memory/RAM to the process (1) so its instructions and data can be stored (1)
• Loads/moves the program instructions into RAM (1) so the process is ready to run (1)
• Adds the process to the ready queue (1) so it can be scheduled onto the CPU (1)
• Gives the process a process ID (PID)/identifier (1) so the operating system can track/manage it (1)

For both marks, the development must follow/be linked to the point.

Only award one of the first two bullets in any one response; allocating memory and loading into RAM are the same stage.

Accept 'memory' for 'RAM' and vice versa.

Accept 'added to a queue for the processor' for the ready queue point.

Do not accept responses that say the process is run on the CPU straight away.

Do not accept descriptions of the program executing/running its instructions, or of the program file being created/saved.

Do not accept responses about the process being blocked or terminated.

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

• A storage limit/quota is set for each user account (1) so the drive is shared fairly between users (1)
• The operating system records how much space each user's files are using (1) and refuses to save more files when the limit is reached (1)
• Each user is given a fixed share/quota of the drive (1) so one user cannot use the space set aside for another (1)

Allow a limit set by an administrator or through the operating system's user management settings; an administrator is not required for credit.

Allow a warning that stops the save; do not award the development for a warning alone where the save is not stopped.

Do not accept responses about passwords/authentication, keeping files separate/folders with no storage limit, deleting old files, compressing files, or buying a larger drive.

Do not accept 'the operating system gives the user a bigger hard drive'.

Do not accept a single global limit for all users; the limit must apply to each user/user account.

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

• It allows the operating system/OS to communicate with the device/printer (1) because it translates the commands into signals the device understands (1)
• It contains/sends the instructions/commands needed by a particular device (1) so the device carries out the correct actions (1)
• It controls the device/printer (1) by sending commands/signals to it (1)
• Different devices need different commands (1) so each one needs its own driver to work with the operating system (1)

For both marks, the expansion must follow/associate with the statement.

Do not accept 'it drives/controls the device' on its own without saying how, e.g. by sending commands/signals.

Do not accept hardware/a physical device (a device driver is software).

Do not accept 'it connects the printer to the computer' or 'it installs the printer' without saying that it provides the instructions/commands for the device.

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.