When you send a friend a photo, the photo does not travel as a photo. It's chopped into hundreds of packets, each stamped with source and destination addresses, each launched into the network to find its own way — possibly along different physical routes, possibly arriving out of order, packet #57 through Kansas City and #58 through Denver. At your friend's phone, they're checked, re-ordered, reassembled — photo again, milliseconds later.
Nobody planned that photo's route. No central computer supervised it. The Internet has no operator, no headquarters, no master switchboard — just tens of thousands of independent networks agreeing to speak the same languages. Those shared languages are called protocols, and they're the entire secret.
The Internet is a network of interconnected computer networks — physical hardware (cables, fiber, routers, wireless links) plus agreed rules for moving data. A computing device is anything that runs programs; a computer network is a group of interconnected computing devices capable of exchanging data. Connected devices communicate along paths — sequences of connected devices between sender and receiver — and routing is finding a path for the data.
Two definitional traps the exam sets:
Data is divided into packets — small chunks, each carrying a piece of the data plus delivery metadata (source address, destination address, sequence information). Key behaviors:
A protocol is an agreed-upon set of rules that lets different devices and networks communicate. The exam's four:
| Protocol | Job | One-line memory hook |
|---|---|---|
| IP (Internet Protocol) | Addressing and routing: every device gets an IP address; packets carry source + destination addresses and get routed toward them | The postal address system |
| TCP (Transmission Control Protocol) | Reliable transport: numbers the packets, confirms arrival, re-requests lost packets, delivers data complete and in order | Certified mail with tracking |
| UDP | Fast transport, no guarantees: sends packets without confirming delivery; lost packets stay lost | Postcards — quick, unconfirmed |
| DNS (Domain Name System) | Translates human-friendly domain names (example.com) into IP addresses | The Internet's phone book |
When you visit a website: DNS translates the name to an IP address → your request is packetized → IP routes each packet → TCP ensures everything arrives, complete and ordered.
TCP vs. UDP is a trade-off question (the exam's favorite kind): TCP's guarantees cost time (confirmations, retransmissions) — right for web pages, email, file downloads, where completeness matters. UDP's speed costs reliability — right for live video calls and gaming, where a lost packet's moment has already passed and re-sending it would only add lag.
(IP addresses come in versions — IPv4's address space ran short, motivating IPv6's vastly larger one. CED-level: know that the addressing system was designed to scale and has evolved; no subnet math will be asked.)
Internet protocols are open standards: publicly documented, free for anyone to implement, maintained cooperatively (standards bodies like the IETF publish them openly). Openness is why any manufacturer's device — any OS, any country — can join the Internet: speak the protocols, and you're in. No licenses, no permission from a central authority.
Scalability is the Internet's capacity to keep working as it grows — millions more devices, no redesign needed. The design choices that make it scale:
Also vocabulary-worthy: bandwidth — the maximum amount of data a connection can transmit in a fixed time (higher bandwidth = more data per second, not "faster electrons").
Problem: You type weatherwatch.example into a browser. Which protocol acts FIRST, and what does it do?
Solution: DNS — the name must become an IP address before anything can be addressed or routed. Then the request is packetized, routed via IP, delivered reliably via TCP.
Interpretation: Sequence questions reward knowing the pipeline: DNS (translate) → IP (address/route) → TCP (guarantee). Names can't be routed; addresses can.
Problem: A 40-packet file transfer arrives with packets in scrambled order and packet 23 missing entirely. Using TCP, what happens?
Solution: TCP reassembles using sequence numbers — scrambled order is routine, not an error. The missing packet 23 is detected (no acknowledgment) and retransmitted by the sender; TCP delivers the complete, correctly ordered file. The user never notices.
Interpretation: "Out of order" and "lost" are expected events with protocol remedies, not failures. An answer choice claiming "the transfer fails" or "the file is corrupted" misunderstands TCP's whole purpose.
Problem: For each application, choose the appropriate transport protocol: (i) downloading a bank statement PDF; (ii) a live video call.
Solution: (i) TCP — a PDF missing packets is corrupt; completeness is everything, and waiting an extra half-second is free. (ii) UDP — the call must flow in real time; a lost packet's audio moment is gone, and retransmitting it would arrive too late to matter, adding delay. Brief glitches beat lag.
Interpretation: The decision rule: does late data still have value? Yes (files, pages, email) → TCP. No (live audio/video, games) → UDP. This mirrors Lesson 4's lossy/lossless reasoning — purpose decides.
Problem: Which characteristic BEST explains how the Internet accommodated growth from thousands to billions of devices without a redesign?
(A) A central agency assigns each new device a route through the network (B) Its open, standardized protocols let new networks and devices join without central approval or coordination (C) Every device connects directly to every other device (D) All data follows one fixed path, so new devices don't affect traffic
Solution: (B). Open standards + decentralization = growth by addition, not redesign. (A) contradicts decentralization; (C) is combinatorially absurd (billions² of links); (D) contradicts dynamic routing.
Interpretation: Scalability answers always combine "open protocols" with "no central authority." Distractors always sneak a central controller or fixed structure back in.
1. (B). Definition, verbatim territory. Protocols are rules, not hardware (A), companies (C), or malware (D).
2. (C). IP = addressing + routing. (A) is DNS; (B) is TCP — and this three-way identity swap is the most common CSN distractor pattern. Drill the table until swaps can't fool you.
3. (B). Packet switching in one sentence: split, independently routed, reassembled. (A) describes circuit switching (old telephone networks — the design the Internet specifically rejected); (D) re-invents the central authority.
4. (D). Names → addresses. Nothing else. (A) inverts it and adds geography; DNS knows no physical locations.
5. (B). Live = latency-sensitive = UDP's trade. (A) is a correct description of TCP attached to the wrong use case — retransmitted video frames arrive too late to show.
6. (C). Loss detection + retransmission = TCP's defining guarantee. (B)/(D) belong to IP addressing and DNS respectively.
7. (B). Infrastructure vs. service-on-infrastructure. The exam asks this distinction nearly verbatim.
8. (C). Public standards → universal joinability → growth. (A), (B), (D) each contradict openness.
9. (B). Data per fixed time — a capacity measure. Higher bandwidth = more data per second.
10. (A) and (C). Both core packet facts. (B) denies independent routing; (D) denies TCP's retransmission remedy.
11. (B). Translate → route → guarantee. The pipeline from Example 1; every other choice scrambles the jobs.
12. (B). Decentralization → permissionless growth → scalability. The exam's favorite CSN conclusion, and the same idea as Example 4 in different clothes.
Answer letter distribution check: B, C, B, D, B, C, B, C, B, A+C, B, B — singles: A×0, B×7, C×4, D×1 + multi (A,C). B-heavy (definitional answers clustered); acknowledged — L18/L19 keys will counterweight with A/D. Cumulative through L17 ≈ A 23%, B 31%, C 26%, D 19%.
No protocols needed in your PT — but there's an exam-day connection worth banking: the reading passage (Q58–62 on the real exam; Lesson 24 trains it) frequently features a networked innovation — a delivery app, a sensor system, a streaming service. Passage questions then quiz this lesson's concepts in context: "the innovation transmits sensor data to a server — which protocol consideration matters?" Your CSN vocabulary (packets, TCP/UDP trade-off, bandwidth, DNS) is what those questions withdraw. CSN content also anchors several of the multi-select items (Q63–70), where two true statements about packets or protocols must both be found.
Mini drill: in one sentence each, say what happens to a food-delivery app's order data at the DNS, IP, and TCP layers. (Model: DNS turns the restaurant API's domain name into an IP address; IP routes the order's packets toward that address hop by hop; TCP confirms every packet arrives and re-requests any that drop, so the order arrives complete.)
1. (B). Definition, verbatim territory. Protocols are rules, not hardware (A), companies (C), or malware (D).
2. (C). IP = addressing + routing. (A) is DNS; (B) is TCP — and this three-way identity swap is the most common CSN distractor pattern. Drill the table until swaps can't fool you.
3. (B). Packet switching in one sentence: split, independently routed, reassembled. (A) describes circuit switching (old telephone networks — the design the Internet specifically rejected); (D) re-invents the central authority.
4. (D). Names → addresses. Nothing else. (A) inverts it and adds geography; DNS knows no physical locations.
5. (B). Live = latency-sensitive = UDP's trade. (A) is a correct description of TCP attached to the wrong use case — retransmitted video frames arrive too late to show.
6. (C). Loss detection + retransmission = TCP's defining guarantee. (B)/(D) belong to IP addressing and DNS respectively.
7. (B). Infrastructure vs. service-on-infrastructure. The exam asks this distinction nearly verbatim.
8. (C). Public standards → universal joinability → growth. (A), (B), (D) each contradict openness.
9. (B). Data per fixed time — a capacity measure. Higher bandwidth = more data per second.
10. (A) and (C). Both core packet facts. (B) denies independent routing; (D) denies TCP's retransmission remedy.
11. (B). Translate → route → guarantee. The pipeline from Example 1; every other choice scrambles the jobs.
12. (B). Decentralization → permissionless growth → scalability. The exam's favorite CSN conclusion, and the same idea as Example 4 in different clothes.
Answer letter distribution check: B, C, B, D, B, C, B, C, B, A+C, B, B — singles: A×0, B×7, C×4, D×1 + multi (A,C). B-heavy (definitional answers clustered); acknowledged — L18/L19 keys will counterweight with A/D. Cumulative through L17 ≈ A 23%, B 31%, C 26%, D 19%.
Exam tip: Make a 4×2 flashcard: IP→addresses/routes, TCP→reliable+ordered+retransmits, UDP→fast+no-guarantees, DNS→names-to-addresses. Most CSN questions are one of these identities wearing a scenario costume — and the distractors are always the other three rows of your flashcard.