Edexcel GCSE Computer Science (1CP2) Exam Questions

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

• Read/view (1)
• Write/edit/modify (1)
• Execute/run (1)
• Delete (1)

Allow 'read only' for read.

Treat write/edit/modify as one right only.

Do not accept 'open' or 'access' on its own.

Do not accept usernames/passwords (these are authentication, not file access rights).

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

• Each student's files/work are kept separate (1) because the operating system checks the access rights of the user who is logged in, so other students cannot open/see/change/delete them (1)
• A student's own settings/desktop are loaded when they log in (1) because the operating system stores settings for each user account (1)
• Students cannot install software or change system settings (1) because their user account does not have administrator privileges (1)

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

Award 1 mark for a correct point on its own, even if no linked reason is given.

Allow answers about personal settings/desktop/wallpaper being saved/loaded for that user.

Allow answers about a standard user account not having administrator privileges.

Do not accept 'so they can log in' on its own, because logging in is what the user account is for.

Do not accept 'so they can save files/work' on its own without saying other students cannot access their files.

Do not accept 'so the computer is secure' without saying what is protected or who is kept out.

Do not accept answers about stopping viruses or making the computer run faster.

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.