AQA A-Level Computer Science: Networking & Communication — Complete Revision Guide (7517)
AQA A-Level Computer Science: Networking & Communication — Complete Revision Guide (7517)
Networking is one of the most heavily examined theory areas of AQA A-Level Computer Science (7517), and it sits in specification area 4.9 — fundamentals of communication and networking. It is also one of the topics where students lose marks not because the ideas are hard, but because they are imprecise: writing "TCP/IP sends the data" when an examiner wants the layer, the protocol, and the unit of data named correctly. The specification rewards students who can describe mechanisms — how a packet is routed, why a digital signature proves integrity, what a subnet mask actually masks — rather than reciting loose definitions.
This material is assessed across both written components. Paper 1 (on-screen, 2 hours 30 minutes, 100 marks, 40% of the A-Level) leans towards programming and computational thinking, but networking concepts surface wherever client-server architecture or data transmission underpins a problem. Paper 2 (written, 2 hours 30 minutes, 100 marks, 40% of the A-Level) is where the bulk of networking theory is tested directly — through definitions, comparisons, calculations on addressing, and extended-response questions that ask you to evaluate a network design or a security measure. The Non-Exam Assessment (NEA, 75 marks, 20%) frequently involves a networked or client-server component, so a solid grasp of these ideas pays off there too.
This guide walks through every lesson in the LearningBro Networking course in a revision-ready narrative. It explains what each concept is, why it matters for the exam, and the pitfalls that cost marks — weaving in direct links to each lesson so you can drill the areas you find weakest.
Guide Overview
This guide covers every lesson in the AQA A-Level Computer Science: Networking course:
- Communication Methods — serial vs parallel, bandwidth, baud rate, bit rate, latency.
- The TCP/IP Protocol Stack — the four layers and what each one does.
- IP Addressing — IPv4, IPv6, subnet masks, NAT, DHCP, public vs private addresses.
- Protocols in Detail — HTTP, HTTPS, FTP, SMTP, POP3, IMAP, DNS and their roles.
- Client-Server and Peer-to-Peer Models — architectures, trade-offs, and where each is used.
- Web Technologies — HTML, CSS, JavaScript, search indexing, and the request-response cycle.
- Encryption and Digital Signatures — symmetric and asymmetric encryption, hashing, digital certificates.
- Network Security — firewalls, proxies, threats, and defensive measures.
- The Internet and the World Wide Web — packet switching, routing, DNS resolution, and how the web sits on the internet.
- Networking Exam Practice — mixed exam-style questions across the whole topic.
Communication Methods: The Vocabulary You Cannot Afford to Confuse
Before you can reason about networks, you need precise language for moving bits between devices. The lesson on communication methods establishes this foundation, and it is worth getting exactly right because the terms appear in nearly every other part of the topic.
Serial transmission sends one bit at a time down a single wire. Parallel transmission sends multiple bits simultaneously across several wires. Intuitively parallel sounds faster, and over short distances it can be — but it suffers from two problems that the exam loves to test. The first is crosstalk, where signals on adjacent wires interfere with one another. The second is skew: bits travelling down separate wires arrive at slightly different times, and over distance this drift makes the data unreadable. This is precisely why modern high-speed links (USB, SATA, PCIe, Ethernet) are serial despite parallel buses once being common — serial avoids skew and can therefore be clocked far faster.
Four measurement terms must be distinguished cleanly:
| Term | Definition | Unit |
|---|---|---|
| Bit rate | Number of bits transmitted per second | bits/second (bps) |
| Baud rate | Number of signal changes (symbols) per second | baud |
| Bandwidth | The range of frequencies a channel can carry | hertz (Hz) |
| Latency | The time delay between sending and receiving | seconds (often ms) |
The relationship bit rate = baud rate × bits per signal change is a classic exam point. If a system uses a modulation scheme that encodes 2 bits per symbol, the bit rate is double the baud rate. Students routinely treat bit rate and baud rate as synonyms — they are only equal when each signal change carries exactly one bit. A useful mental model: bandwidth is how wide the road is, latency is how long the journey takes, and bit rate is how many cars actually pass per second. A satellite link can have high bandwidth yet high latency, because the signal travels roughly 36,000 km to a geostationary satellite and back, which is why it feels sluggish for interactive work even when it carries plenty of data.
The TCP/IP Protocol Stack: Layering as a Design Principle
The TCP/IP protocol stack is the conceptual spine of the whole networking topic. AQA examines the four-layer model, and you must be able to name each layer, state its responsibility, and give example protocols that operate there.
| Layer | Responsibility | Example protocols |
|---|---|---|
| Application | Provides services and an interface to user-facing programs | HTTP, HTTPS, FTP, SMTP, IMAP, POP3, DNS |
| Transport | End-to-end communication, segmentation, reliability, ports | TCP, UDP |
| Network (Internet) | Logical addressing and routing across networks | IP, ICMP |
| Link (Network Interface / Data Link) | Physical transmission on the local medium, MAC addressing | Ethernet, Wi-Fi (802.11) |
The single most important idea here is why layering exists. Each layer provides a service to the layer above and relies on the service of the layer below, but the layers are independent — you can swap Wi-Fi for Ethernet at the link layer without touching anything in the application layer. This separation of concerns makes the internet extensible and maintainable, and "explain the benefit of a layered model" is a recurring exam question. The expected points are: it simplifies design and troubleshooting, it allows components from different vendors to interoperate, and a change in one layer does not force changes in the others.
A second high-value idea is encapsulation. As data descends the stack, each layer adds its own header (and the link layer adds a trailer). The application data becomes a transport-layer segment, then a network-layer packet (or datagram), then a link-layer frame. On the receiving device the process reverses — each layer strips its own header. Using the correct unit of data for each layer is a frequent discriminator between a full-mark and a near-miss answer. Common pitfall: calling everything a "packet". A packet is specifically the network-layer unit.
IP Addressing: Where Precision Earns Marks
The lesson on IP addressing is the most technically demanding part of the topic and a reliable source of calculation marks. AQA expects fluency with IPv4 structure, subnetting, and the supporting services that keep the address space usable.
An IPv4 address is 32 bits, written as four dotted-decimal octets (for example 192.168.0.1). That gives roughly 4.3 billion addresses, which the growth of internet-connected devices has effectively exhausted. IPv6 is 128 bits, written as eight hexadecimal groups (for example 2001:0db8:85a3:0000:0000:8a2e:0370:7334), providing an address space so large it is, for practical purposes, inexhaustible. IPv6 also simplifies headers and removes the routine need for NAT.
A subnet mask separates an IP address into a network portion and a host portion. With a mask of 255.255.255.0 (written /24 in CIDR notation), the first 24 bits identify the network and the remaining 8 identify the host. The exam frequently asks you to work out usable host counts. The rule is that two host addresses on each subnet are reserved — the all-zeros network address and the all-ones broadcast address — so a /24 subnet provides 2^8 − 2 = 254 usable host addresses.
| CIDR | Subnet mask | Host bits | Usable hosts |
|---|---|---|---|
| /24 | 255.255.255.0 | 8 | 254 |
| /25 | 255.255.255.128 | 7 | 126 |
| /26 | 255.255.255.192 | 6 | 62 |
| /27 | 255.255.255.224 | 5 | 30 |
Three supporting mechanisms complete the picture, and AQA expects you to explain each:
- NAT (Network Address Translation) lets many devices on a private network share a single public IP address. The router rewrites source addresses and ports on outgoing packets and reverses the translation on the replies. NAT is a major reason IPv4 has lasted as long as it has, because it conserves public addresses.
- DHCP (Dynamic Host Configuration Protocol) automatically assigns IP addresses (and gateway and DNS settings) to devices as they join a network, removing the need for manual configuration and avoiding address clashes.
- Private address ranges (such as
192.168.x.xand10.x.x.x) are reserved for internal networks and are never routed on the public internet — packets bound for a private address must go through NAT to reach the outside world.
A common pitfall is forgetting the "minus 2" when counting hosts, or confusing the routable status of private addresses. Practising a handful of subnet calculations until they are automatic is one of the highest-return revision activities for this topic.
Protocols in Detail: Knowing the Right Tool for the Job
The protocols in detail lesson moves from the structure of the stack to the specific application-layer protocols you must know by name, purpose, and typical port. The exam will not usually ask for port numbers, but it will absolutely ask what a protocol does and when you would use it.
| Protocol | Purpose |
|---|---|
| HTTP | Transfers web pages between server and browser (unencrypted) |
| HTTPS | HTTP secured with TLS, encrypting traffic between client and server |
| FTP | Transfers files between hosts |
| SMTP | Sends email from a client to a server, and between mail servers |
| POP3 | Retrieves email, typically downloading and removing it from the server |
| IMAP | Retrieves email while keeping it synchronised on the server across devices |
| DNS | Resolves human-readable domain names into IP addresses |
The distinctions that earn marks are the subtle ones. SMTP is for sending; POP3 and IMAP are for retrieving — a classic confusion is to claim SMTP receives mail. POP3 versus IMAP is another favourite: POP3 typically downloads messages to one device and deletes them from the server, whereas IMAP leaves messages on the server and synchronises state (read/unread, folders) across all your devices — which is why modern multi-device email almost always uses IMAP. For the transport layer, you must justify TCP versus UDP: TCP is connection-oriented and reliable, with acknowledgements, retransmission, ordering, and flow control, making it right for web pages, email and file transfer; UDP is connectionless and unreliable but has lower overhead, making it right for live video, voice and online gaming where a late packet is worse than a lost one.
Client-Server and Peer-to-Peer Models
The client-server and peer-to-peer models lesson covers the two dominant ways of organising a networked application, and "compare and evaluate" questions on this pairing appear regularly.
In the client-server model, dedicated servers provide resources or services to requesting clients. The server centralises data, authentication and security. This makes management, backup and access control straightforward, but it creates a single point of failure and a potential bottleneck under heavy load. The web itself is the canonical example: browsers (clients) request pages from web servers.
In the peer-to-peer (P2P) model, every node acts as both a client and a server, sharing resources directly with other peers. There is no central authority. P2P networks are resilient (no single point of failure) and scale naturally as peers join and contribute resources — file-distribution systems like BitTorrent rely on this. The trade-off is that security, consistency and management are far harder without a central point of control, and content can be difficult to locate and police.
When evaluating, avoid the vague "client-server is better" trap. The right answer ties features to context: a school's central record system suits client-server because access control and backup matter most; a large-scale file distribution suits P2P because resilience and scalability matter most and there is no need for centralised control.
Web Technologies and the Request-Response Cycle
The web technologies lesson connects the abstract network to what users actually experience in a browser. HTML defines structure and content, CSS controls presentation and layout, and JavaScript adds interactivity that runs client-side in the browser. AQA expects you to know the division of labour cleanly — for instance, that JavaScript executing in the browser is client-side processing, distinct from server-side code that queries a database and generates pages.
The request-response cycle is the mechanism to internalise: the browser sends an HTTP(S) request, the server processes it (possibly running server-side code and querying a database), and returns a response containing the page. This lesson also covers how search engines build their indexes — crawling pages, indexing content, and ranking results — which connects neatly to the broader idea of how information is located on the web. A pitfall here is blurring client-side and server-side responsibilities; be ready to state explicitly where each piece of processing happens and why (for example, validation should occur server-side for security even if it also happens client-side for responsiveness).
Encryption and Digital Signatures: The Logic of Trust
Security is where AQA 7517 has become more demanding, and the encryption and digital signatures lesson is essential. You must be able to explain the mechanisms, not merely state that "data is encrypted".
Symmetric encryption uses the same key to encrypt and decrypt. It is fast and efficient, but it has the key-distribution problem: how do two parties agree on a shared secret key over an insecure channel without an eavesdropper intercepting it?
Asymmetric encryption solves this using a mathematically linked key pair — a public key that can be shared freely and a private key kept secret. Anything encrypted with the public key can only be decrypted with the matching private key. So anyone can encrypt a message to you using your public key, but only you can read it. The trade-off is that asymmetric encryption is computationally expensive, which is why real systems use a hybrid approach: asymmetric encryption to exchange a one-time symmetric session key, then fast symmetric encryption for the actual data.
Hashing must be distinguished from encryption. A hash function maps input data of any size to a fixed-size value and is one-way — you cannot reverse a hash to recover the original. A small change in the input produces a completely different hash. Hashing is therefore used for integrity checking and for storing passwords, not for confidential transmission. Confusing hashing with encryption is one of the most common and costly errors in this topic.
Digital signatures combine hashing and asymmetric encryption to prove both authenticity (the message genuinely came from the claimed sender) and integrity (it has not been altered). The mechanism, which you should be able to reproduce step by step:
- The sender computes a hash (digest) of the message.
- The sender encrypts that hash with their private key — this is the signature.
- The sender transmits the message together with the signature.
- The recipient decrypts the signature using the sender's public key, recovering the original hash.
- The recipient independently hashes the received message and compares it with the recovered hash.
- If the two hashes match, the message is authentic and unaltered.
Digital certificates close the remaining gap — how do you trust that a public key really belongs to who it claims to? A certificate is issued by a trusted Certificate Authority (CA) and binds a public key to an identity; it contains the holder's details, the public key, the issuing CA, and an expiry date, all signed by the CA. This is the chain of trust that underpins HTTPS. Note the direction of the keys carefully: for confidentiality you encrypt with the recipient's public key; for a signature you encrypt the hash with the sender's private key. Getting these the right way round is exactly what distinguishes a strong answer.
Network Security: Threats and Defences
The network security lesson rounds out the topic with the practical defences that protect networks and the threats they counter.
A firewall monitors and filters traffic against a set of rules, blocking unauthorised connections. Packet filtering inspects each packet's source, destination and port, while a stateful firewall also tracks the state of active connections to make smarter decisions. A proxy server sits between clients and the wider internet, forwarding requests on the clients' behalf; it can cache content to improve performance, filter or log requests, and hide the internal addresses of clients for privacy.
On the threat side, you should be able to describe common attacks and their countermeasures:
- Malware (viruses, worms, trojans, ransomware) — mitigated by anti-malware software, patching, and user education.
- SQL injection — inserting malicious SQL through unvalidated input; mitigated by input validation and parameterised queries.
- Denial of Service (DoS/DDoS) — overwhelming a service with traffic; mitigated by firewalls, rate limiting and traffic filtering.
- Social engineering and phishing — manipulating people rather than systems; mitigated chiefly by training and authentication controls.
The recurring exam skill is to pair each threat with a specific, appropriate defence and to justify it. A blanket "use a firewall" is a weak answer to a phishing question, because phishing targets human behaviour rather than packets — the credible defences are user education and multi-factor authentication.
The Internet and the World Wide Web: Tying It Together
The internet and the World Wide Web lesson assembles everything into a coherent end-to-end picture and clears up a distinction students frequently muddle. The internet is the global infrastructure of interconnected networks; the World Wide Web is one service that runs on top of the internet, delivering linked pages over HTTP(S). The web is not the internet — email and file transfer also use the internet but are not part of the web.
The internet uses packet switching: data is split into packets, each routed independently and possibly along different paths, then reassembled at the destination. This is contrasted with circuit switching (as in traditional telephony), which reserves a dedicated path for the whole conversation. Packet switching is more efficient because network capacity is shared rather than tied up by idle connections, and it is more resilient because routers can dynamically reroute packets around failed or congested links. Be ready to explain the role of routers in examining a packet's destination address and forwarding it towards its destination.
Finally, DNS resolution stitches the human-readable web to the numeric network: when you enter a domain, a DNS lookup returns the server's IP address, and only then can a connection be made. This is the natural point at which addressing, protocols and routing all meet — a frequent setting for extended-response questions that ask you to trace what happens "from typing a URL to seeing the page".
Putting It Into Practice
Networking rewards methodical, precise revision more than almost any other 7517 topic, because so many marks turn on naming the right layer, the right protocol, or the right key. The networking exam practice lesson brings the strands together with mixed questions in the style and depth AQA expects, so you can find the gaps before the exam does. Two habits matter most: when you describe a process (the fetch of a page, a digital signature, a subnet calculation), write each step explicitly; and when you compare or evaluate, anchor every point to the scenario rather than reciting generic pros and cons.
Next Steps
Work through the AQA A-Level Computer Science: Networking course in order, using the lesson links above to target your weakest areas first — subnetting and the digital-signature mechanism are the two highest-yield places to invest time. Then set the topic in the context of the wider qualification by following the A-Level Computer Science (AQA) learning path, which sequences networking alongside architecture, databases and the programming components so your revision builds towards Paper 1 and Paper 2 together.