GCSE Computer Science
Questions
& Model Answers

Not a bank of questions with the answers printed underneath. The three banded responses are the starting point, not the output: what follows each one is the discriminator, named out loud, then the questions you actually ask to move a student from the first answer to the last, then the mark scheme that shows what each line was worth.

Computer science needs more than written model answers, so it gets them. Completed trace tables where every pass has its own row. Pseudocode listings with the line numbers the question refers to. Binary and hexadecimal working set out column by column. File-size calculations marked step by step, each step saying what it still earns when the number coming into it is wrong. Truth tables, logic circuits drawn in code, database tables and SQL queries. Every calculation is recomputed from the built page on every build, every truth table is regenerated from the expression printed beside it, and every SQL query is executed against the table it sits next to.

The assessment objectives are the one thing the boards do not choose. Ofqual sets AO1 at 30%, AO2 at 40% and AO3 at 30%, and all four specifications carry exactly that. This book is weighted to it by marks — not by question count, which is the easy way to look balanced and be wrong — and the build stops if any objective drifts more than three points. The first draft came out at 18/36/46, because evaluation is the interesting part to write and nothing on a page would ever have shown it.

Where the four boards differ, the book says so on the page. That is not a disclaimer, it is a page: every divergence listed against the questions it affects. AQA states in terms that "knowledge of specific registers is not required", and examines no network topologies at all. Its binary arithmetic will not carry beyond the eighth bit, so overflow sits outside what it assesses. Its cyber-security threat list does not include brute-force or denial-of-service attacks. SQL is not in the Department for Education document at all, and the four boards do four different things with it — a full topic for one, three keywords for another, nothing whatever for the third.

A book that spent nine questions on SQL would be spending nine questions on content half the market never sits. This one spends five, and prints the reason.

Everything else is common ground, and that is checked rather than claimed. Every question is anchored to a phrase in the Department for Education subject content, resolved against the published document on every build, and the build fails if a phrase is not there or if a board is named on a page that carries no note. Nine questions carry one. The rest name nobody.

Written to

The GCSE subject content for computer science published by the Department for Education, updated 31 March 2025 for teaching from September 2025, with all four current specifications read against it — AQA 8525 version 1.3, OCR J277 version 3.1, Pearson Edexcel 1CP2 and WJEC Eduqas

Intended for

computer science teachers and heads of department — used with a class, not a student revision guide

Extent

106 pages · 9 sections