Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/autopilot.md
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,8 @@ The owner's priority since 2026-11-03: proper exam practice. The design, decisio
- [x] Microprocessors: +34 (10 → 44), 3 for each of the 11 taught lessons (4 for segments), each with `lesson` and (all but one) `section`. (PR #94, stacked on #91)
- [x] Computer Organization: +26 (10 → 36), 2 or 3 for each of the 9 taught lessons, each with `lesson` and `section`. (PR #96, stacked on #94)
- [x] Discrete Mathematics: +26 (42 → 68), 1 or 2 for each of the 17 taught lessons, each with `lesson` and `section`. (PR #101)
- Still to do, measured 2026-11-16: Data Structures 20, Computer Networks 9. Advanced Software Engineering (42) is new and left to its authors.
- [x] Data Structures: +20 (28 → 48) and Computer Networks: +9 (27 → 36), 1 or 2 per taught lesson, each with `lesson` and `section`. (PR #102, stacked on #101)
- 4c is done for every course except Logic Design and Computer Architecture (inline practice, owner's decision pending), Algorithm Design (owner's) and Advanced Software Engineering (its authors').
- [ ] 4d. Set `lesson`/`section` on the 259 migrated questions.
- [ ] 5. Generated questions (subnets, scheduling, Big-O first).
- [ ] 6. Account sync for review cards and exam attempts.
Expand Down Expand Up @@ -93,6 +94,7 @@ Nothing. The exam-stack block (since 2026-11-06, over #68's inline practice ques

Newest first. One line per run: date and run, what was done, PR link, merged or open.

- 2026-11-18 10:40 (run B): exam phase 4c, the last two courses: Data Structures +20 and Computer Networks +9, numbers checked by script (g[2][1] at 1036, 31 copies for 17 doubling appends, ring back at index 1, heap parent of 9 is 4, 10 ms over 2,000 km, cwnd 16 after 4 slow-start round trips). Next exam phase: 4d, tagging the 259 migrated quiz questions with `lesson` and `section`. PR #102, open, stacked on #101.
- 2026-11-18 06:10 (run A): the owner merged everything on 2026-11-17 (the exam stack #90 to #96, #86, #92, #99, #100), so this phase branches from main again. Exam phase 4c, Discrete Mathematics: +26 questions over all 17 taught lessons (precedence, vacuous truth, contrapositive vs converse, nested quantifiers, composition order, partial orders, proof setups, the base case, strong induction, invariant checks, sum and product rules, binomial and Pascal, pigeonhole, K₇, Euler vs Hamiltonian, tree height, expectation, birthday pairs), numbers checked by script. PR #101, open.
- 2026-11-17 14:50 (run C): from the 2026-11-12 audit, the Computer Organization `bits-and-bytes` unit ladder (124 px too wide at 390 px) now fits. Its captions now sit under their bars in a two-column grid at every width, which also fixes the desktop TB and PB captions wrapping unindented, and "2^0 = 1 bytes" now reads "1 byte". PR #99, open. Its CI check is red only because main is: The Exam Mind's round 7 (#97) renamed a heading that a bank question points at; fixed in PR #100.
- 2026-11-17 10:40 (run B): exam phase 4c, Computer Organization: +26 questions over all 9 taught lessons, numbers checked by script (500 GB shown as 465.7, G = 01000111, 2¹⁶ and 2¹² locations, the disk capacity 516,096,000 bytes, 4.2 ms average wait at 7,200 rpm). PR #96, open, stacked on #94.
Expand Down
126 changes: 126 additions & 0 deletions src/content/computer-networks/questions.ts
Original file line number Diff line number Diff line change
Expand Up @@ -355,4 +355,130 @@ export const questions: Question[] = [
correctOptionId: "b",
explanation: "304 Not Modified means the cached version is still current, so no body is sent. Redirects are 301, 302, 307 and 308.",
},
{
id: "computer-networks/layers-and-packets/encapsulation",
lesson: "layers-and-packets",
section: "encapsulation",
prompt: "A browser sends an HTTP request. From outermost to innermost, how is it wrapped on the wire?",
options: [
{ id: "a", text: "HTTP, then TCP, then IP, then the link frame" },
{ id: "b", text: "Link frame, then IP, then TCP, then HTTP" },
{ id: "c", text: "IP, then link frame, then TCP, then HTTP" },
{ id: "d", text: "TCP, then IP, then HTTP, then link frame" },
],
correctOptionId: "b",
explanation: "Going down the stack each layer wraps what it got: TCP wraps the HTTP data, IP wraps the segment, and the link layer wraps the IP packet in a frame. So the outermost is the link frame and the innermost is HTTP. The first option lists the order they're added, inside out.",
},
{
id: "computer-networks/delay-and-throughput/propagation",
lesson: "delay-and-throughput",
section: "four-kinds-of-delay",
prompt: "Signals travel at about 2 × 10⁸ m/s in fibre. What is the propagation delay over 2,000 km?",
options: [
{ id: "a", text: "1 ms" },
{ id: "b", text: "100 ms" },
{ id: "c", text: "10 ms" },
{ id: "d", text: "It depends on the link's bandwidth" },
],
correctOptionId: "c",
explanation: "d / v = 2,000,000 m ÷ 2 × 10⁸ m/s = 0.01 s = 10 ms. Propagation depends on the link's length, not its bandwidth; bandwidth sets the transmission delay instead.",
},
{
id: "computer-networks/ip-addresses-and-subnets/private",
lesson: "ip-addresses-and-subnets",
section: "private-addresses-and-nat",
prompt: "Which of these addresses is NOT in a private range?",
options: [
{ id: "a", text: "10.20.30.40" },
{ id: "b", text: "192.168.0.1" },
{ id: "c", text: "172.20.1.1" },
{ id: "d", text: "172.32.1.1" },
],
correctOptionId: "d",
explanation: "The private ranges are 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16. A /12 starting at 172.16 covers 172.16 to 172.31, so 172.20.1.1 is private but 172.32.1.1 is just past the range and public.",
},
{
id: "computer-networks/routing/forwarding-vs-routing",
lesson: "routing",
section: "forwarding-and-routing",
prompt: "What's the difference between forwarding and routing?",
options: [
{ id: "a", text: "Forwarding sends each packet out by a table lookup, in nanoseconds; routing fills in the tables, over seconds to minutes" },
{ id: "b", text: "They're two names for the same job" },
{ id: "c", text: "Routing happens per packet; forwarding happens once a day" },
{ id: "d", text: "Forwarding is for TCP and routing is for UDP" },
],
correctOptionId: "a",
explanation: "Forwarding is the per-packet job: look up the destination in the forwarding table and send it out, in hardware. Routing is how those tables get computed, by routers exchanging information, in software.",
},
{
id: "computer-networks/udp-and-ports/no-promises",
lesson: "udp-and-ports",
section: "udp-just-ports-and-a-checksum",
prompt: "An app sends three UDP datagrams. What can the receiver rely on?",
options: [
{ id: "a", text: "All three arrive, in order" },
{ id: "b", text: "All three arrive, in any order" },
{ id: "c", text: "Each one that arrives is whole, but some may be lost or arrive out of order" },
{ id: "d", text: "They arrive merged into one stream" },
],
correctOptionId: "c",
explanation: "UDP adds only ports and a checksum to IP. Each datagram is delivered whole or not at all, with no guarantee of delivery or order. Merging into a byte stream is TCP's behaviour.",
},
{
id: "computer-networks/tcp-reliable-delivery/handshake",
lesson: "tcp-reliable-delivery",
section: "the-three-way-handshake",
prompt: "What are the three messages of TCP's handshake, in order?",
options: [
{ id: "a", text: "SYN, ACK, FIN" },
{ id: "b", text: "SYN, SYN-ACK, ACK" },
{ id: "c", text: "ACK, SYN, SYN-ACK" },
{ id: "d", text: "HELLO, SYN, ACK" },
],
correctOptionId: "b",
explanation: "The client sends SYN with its starting number, the server answers SYN-ACK with its own number and acknowledges the client's, and the client ACKs the server's. It costs one round trip before data. FIN is for closing.",
},
{
id: "computer-networks/congestion-control/slow-start",
lesson: "congestion-control",
section: "slow-start-then-additive-increase",
prompt: "A new TCP connection starts in slow start with cwnd = 1 segment. If nothing is lost, what is cwnd after 4 round trips?",
options: [
{ id: "a", text: "5" },
{ id: "b", text: "4" },
{ id: "c", text: "8" },
{ id: "d", text: "16" },
],
correctOptionId: "d",
explanation: "Slow start doubles cwnd every round trip: 1 → 2 → 4 → 8 → 16. Despite the name it grows exponentially. Adding one per round trip, which gives 5, is congestion avoidance, after cwnd reaches ssthresh.",
},
{
id: "computer-networks/dns/record-types",
lesson: "dns",
section: "record-types",
prompt: "Which DNS record says where email for a domain should be delivered?",
options: [
{ id: "a", text: "MX" },
{ id: "b", text: "AAAA" },
{ id: "c", text: "CNAME" },
{ id: "d", text: "NS" },
],
correctOptionId: "a",
explanation: "MX records name a domain's mail servers. AAAA maps a name to an IPv6 address, CNAME makes a name an alias for another, and NS names the authoritative servers for a zone.",
},
{
id: "computer-networks/http-and-https/cookies",
lesson: "http-and-https",
section: "stateless-with-cookies",
prompt: "HTTP is stateless, so how does a website keep you signed in from one page to the next?",
options: [
{ id: "a", text: "The TCP connection stays open while you browse" },
{ id: "b", text: "The server sends a cookie, and the browser sends it back with every request" },
{ id: "c", text: "The server remembers your IP address" },
{ id: "d", text: "HTTPS keeps the session automatically" },
],
correctOptionId: "b",
explanation: "Each request stands alone, so the server hands the browser a cookie (Set-Cookie) and the browser includes it on later requests. That lets any server machine recognise you. IP addresses are shared and change, so they can't identify a session.",
},
];
Loading
Loading