You are viewing a free preview of this lesson.
Subscribe to unlock all 4 lessons in this course and every other course on LearningBro.
Paper 2 of the AQA A-Level Computer Science exam contains extended-answer questions worth 8–12 marks and a Section C based on Preliminary Material that is released in advance. This lesson covers how to structure technical essays, how to prepare for the Preliminary Material, and the specific techniques that earn marks on the highest-value questions.
Extended-answer questions are the highest-value individual questions on Paper 2. They typically carry 8–12 marks and require you to write a sustained, well-structured response that demonstrates depth of knowledge, application to context, and reasoned evaluation.
| Criterion | What It Means | How to Demonstrate It |
|---|---|---|
| Technical accuracy | Using correct CS terminology and demonstrating accurate understanding | Define key terms precisely; use technical vocabulary naturally |
| Depth of explanation | Going beyond surface-level description to explain how and why | Explain mechanisms, not just names; show you understand the underlying processes |
| Application to context | Relating your answer to the specific scenario in the question | Refer explicitly to the scenario; explain how the concept applies in this case |
| Balanced evaluation | Considering multiple perspectives, advantages and disadvantages | Discuss at least two sides; weigh trade-offs; avoid one-sided answers |
| Reasoned judgement | Reaching a clear conclusion based on your analysis | End with a justified conclusion that follows from your argument |
| Logical structure | Organising your answer coherently | Use paragraphs; present related points together; build towards your conclusion |
Use the following framework for every extended-answer question:
Step 1: Define key terms (1–2 sentences) Start by defining the core technical concept(s) in the question. This immediately shows the examiner you understand the topic and earns AO1 marks.
Step 2: Explain the concept in detail (2–3 paragraphs) Explain how the concept works, including technical details. Use specific examples, named algorithms, or concrete scenarios. This is where the bulk of your AO1 and AO2 marks come from.
Step 3: Apply to the scenario (1–2 paragraphs) If the question refers to a scenario (especially in Section C), explicitly connect your explanation to the details of the scenario. Say "In this scenario, the hotel booking system would benefit from... because..." rather than making generic statements.
Step 4: Evaluate trade-offs (1–2 paragraphs) Discuss advantages and disadvantages, or compare alternatives. Use technical language and give specific reasons. Avoid vague statements like "it is faster" — instead say "binary search has O(log n) time complexity compared to O(n) for linear search, which is significant when the hotel has 10,000 records."
Step 5: Conclude with a reasoned judgement (1–2 sentences) Make a clear recommendation or judgement that follows logically from your analysis. "Given that the system needs to handle high volumes of concurrent bookings, a client-server architecture with a normalised relational database would be the most appropriate choice because..."
Exam Tip: Extended-answer questions are marked using a levels-based mark scheme. To reach the top level (typically Level 3), you must demonstrate all of: technical accuracy, application to context, balanced evaluation, and a reasoned conclusion. Missing any of these caps your mark at a lower level.
Certain topics appear repeatedly in extended-answer questions on Paper 2. Preparing structured responses for these topics gives you a significant advantage.
| What to Know | Detail |
|---|---|
| Key complexities | O(1) constant, O(log n) logarithmic, O(n) linear, O(n log n) linearithmic, O(n^2) quadratic, O(2^n) exponential |
| Common comparisons | Linear vs binary search; bubble sort vs merge sort; sequential vs indexed file access |
| What to discuss | Time complexity, space complexity, trade-offs between the two |
| How to apply | Relate to the specific data sizes in the scenario — "With 50,000 customer records, the difference between O(n) and O(log n) is the difference between 50,000 comparisons and approximately 16" |
| What to Know | Detail |
|---|---|
| Forms | UNF (unnormalised form), 1NF (no repeating groups, atomic values), 2NF (no partial dependencies), 3NF (no transitive dependencies) |
| Advantages of normalisation | Reduces data redundancy, prevents update anomalies (insertion, deletion, modification), ensures data integrity |
| Disadvantages of normalisation | More tables mean more complex queries, JOIN operations can be slower, may reduce read performance |
| When to discuss denormalisation | Read-heavy systems, data warehousing, reporting databases — situations where query speed matters more than write integrity |
| What to Know | Detail |
|---|---|
| Lossy compression | Permanently removes data; smaller file sizes; used for multimedia (JPEG, MP3, MPEG) |
| Lossless compression | No data lost; file can be perfectly reconstructed; used for text, executables, archives (ZIP, PNG, FLAC) |
| Common algorithms | Run-length encoding (RLE), Huffman coding, dictionary-based (LZW) |
| What to discuss | Trade-off between file size and quality/accuracy; suitability for different data types; compression ratios |
| What to Know | Detail |
|---|---|
| TCP/IP layers | Application, Transport, Internet, Link |
| Key protocols | HTTP/HTTPS (web), FTP (file transfer), SMTP/IMAP/POP3 (email), TCP (reliable transport), UDP (fast but unreliable), IP (addressing and routing), DNS (name resolution) |
| TCP vs UDP | TCP: connection-oriented, guaranteed delivery, error checking, ordering — used for web, email, file transfer. UDP: connectionless, no guaranteed delivery, lower overhead — used for streaming, gaming, VoIP |
| Client-server vs peer-to-peer | Client-server: centralised control, easier to manage, single point of failure. Peer-to-peer: distributed, resilient, harder to manage, security challenges |
| What to Know | Detail |
|---|---|
| Key legislation | Data Protection Act 2018 (UK GDPR), Computer Misuse Act 1990, Copyright Designs and Patents Act 1988, Regulation of Investigatory Powers Act 2000 |
| Ethical issues | Privacy, surveillance, AI bias, autonomous vehicles, digital divide, environmental impact of computing |
| Moral issues | What is right vs wrong in computing contexts — whistleblowing, responsible disclosure of vulnerabilities, use of personal data |
| How to structure | Define the issue; explain the relevant legislation or ethical principle; apply to the scenario; discuss different stakeholder perspectives; reach a conclusion |
Exam Tip: For ethics questions, avoid vague generalisations like "this raises privacy concerns." Instead, be specific: "Under the Data Protection Act 2018, personal data must be processed for a specified, explicit and legitimate purpose. Collecting location data from users without their explicit consent would violate this principle."
The Preliminary Material is the defining feature of Paper 2 Section C. Understanding how to prepare for it is a critical exam technique.
The Preliminary Material describes a real-world computing scenario. Past scenarios have included:
| Example Type | What It Might Describe |
|---|---|
| Business system | A hotel booking system, a library management system, an online retail platform |
| Data processing | A scientific data collection and analysis system, a weather monitoring network |
| Social/community | A social media platform, a community messaging system, a crowdsourcing application |
| Technical infrastructure | A network design for a school, a cloud-based storage system, a distributed database |
The scenario will typically include details about:
AQA releases a new Preliminary Material for each exam series. The scenario is always different, but the types of questions asked are consistent. This means your preparation strategy should focus on:
| Phase | When | What to Do |
|---|---|---|
| Phase 1: First read | As soon as it is released | Read the entire Preliminary Material once without taking notes. Get a general understanding of the scenario. |
| Phase 2: Annotate | Within the first week | Re-read the document carefully. Highlight or annotate key details: data types, volumes, users, requirements, constraints. |
| Phase 3: Topic mapping | Week 1–2 | For each section of the AQA specification, ask: "How does this topic apply to this scenario?" Write notes mapping topics to the scenario. |
| Phase 4: Practice questions | Week 2–4 | Write practice answers applying CS concepts to the scenario. Use past papers from different years and adapt the questions to the current scenario. |
| Phase 5: Review | Final week | Review your annotations and topic mapping. Ensure you can discuss at least 8–10 different CS topics in the context of this scenario. |
For each of these topics, prepare notes on how it relates to the Preliminary Material scenario:
Subscribe to continue reading
Get full access to this lesson and all 4 lessons in this course.