Computer Networks intimidates through volume — dozens of protocols, layers, acronyms — but the exam’s structure is generous: it follows the layer architecture itself, drawing its repeating questions from each layer’s greatest hits. Study by layers, master the handful of numericals, and CN’s sprawl becomes an outline. (Align to your regulation’s units; verify with recent papers.)
The repeating families, layer by layer
- Fundamentals: the OSI vs TCP/IP comparison — arguably the single most repeated question in the subject (a labelled layer diagram with per-layer functions is a rehearsable full answer); network topologies; switching (circuit vs packet); performance terms (bandwidth, latency, throughput) for Part A.
- Data link layer: framing and error control — CRC computation (a mechanical numerical: given data and generator, compute the codeword) and checksum/parity concepts; flow control — stop-and-wait and sliding-window protocols (Go-Back-N vs Selective Repeat with window diagrams is a perennial 13-marker); medium access — CSMA/CD and Ethernet basics; wireless MAC concepts per syllabus.
- Network layer — the numerical heart: IPv4 addressing and the exam’s numerical signature — subnetting: given an address block, derive subnet masks, ranges, usable hosts, or design subnets for stated requirements. Practise ten of these; some variant is close to guaranteed. Then IPv4 vs IPv6 (comparison-table friendly), and routing algorithms — distance-vector vs link-state, with Dijkstra traced on a given topology (the same trace discipline as DS — one preparation, two papers). ARP/ICMP/DHCP populate Part A.
- Transport layer: the TCP vs UDP comparison (another rehearsable staple); the three-way handshake with its segment diagram; TCP flow/congestion control (slow start, AIMD — a favourite “explain with graph” 13-marker); connection termination.
- Application layer: how DNS resolution works end-to-end (diagram-friendly and frequently asked); HTTP basics; email protocols (SMTP/POP/IMAP roles); FTP; plus per-regulation tails (SNMP, security basics) as either-or options.
The examiner’s lens — diagrams and comparisons
CN valuers reward two answer shapes above all. Labelled diagrams: the layer stack, sliding windows in motion, the handshake’s three arrows, DNS’s resolution chain — each is worth real marks and calms the rest of the answer. Comparison tables: OSI/TCP-IP, TCP/UDP, IPv4/IPv6, GBN/SR — a clean 6-row table with a summary line is a complete, high-scoring 13-mark answer format this paper accepts unusually well. For numericals (CRC, subnetting, Dijkstra), the OS rule applies: stepwise working carries the marks. Build a one-page diagram sheet and a one-page comparison sheet per unit — they become your entire final revision.
The industry echo
Networking literacy is quietly load-bearing across careers: interviews ask TCP/UDP and DNS constantly (our interview-basics post covers that framing), cloud/DevOps work assumes subnetting fluency (VPCs are subnetting with a console), and security careers are networking with an adversary. The subnetting you drill for this paper configures real infrastructure within two years for many graduates.
The 2-week subject plan
- Days 1-2: frequency-map your papers; build the layer-wise topic checklist.
- Days 3-7: one layer per day — learn the family, draw its diagrams from memory, build its comparison tables, and do its numericals (CRC day 4, subnetting drills days 5-6, Dijkstra day 7).
- Days 8-9: subnetting bootcamp — ten varied problems to fluency; this is the paper’s highest-certainty investment.
- Days 10-11: 2-mark sweep layer-wise (port numbers, protocol one-liners, header fields your syllabus emphasises).
- Days 12-14: timed full paper → autopsy → revise only the diagram and comparison sheets. Sleep.