OSI model — 7 layers, responsibilities, PDU names: Question bank

Recall What every trap here is really testing

Almost every OSI mistake is a layer mix-up: putting a job (routing, ports, encryption, MAC) at the wrong floor of the stack, or forgetting that PDU names come from wrapping, not from content. Keep the elevator picture in mind: data rides DOWN the 7 floors on the sender, UP on the receiver, gaining a wrapper per floor down.

True or false — justify

True or false: "The OSI model is the actual software running on your computer right now."

False. OSI is a reference blueprint (ISO, 1984), not deployed code; the real Internet runs the TCP/IP stack. OSI is the map, TCP/IP is the road built.

True or false: "Data physically travels sideways from Layer 4 on machine A to Layer 4 on machine B."

False. Data only moves down the sender's stack and up the receiver's; the horizontal "peer-to-peer" arrow is a logical conversation, not a physical wire.

True or false: "The PDU name changes because the data inside actually becomes different information."

False. The payload is unchanged; only a new header (and an L2 trailer) is wrapped around it. New wrapper = new name (Data→Segment→Packet→Frame→Bits).

True or false: "A frame is always smaller than the application data it carries."

False. Encapsulation is purely additive — each layer prepends metadata and removes nothing, so the on-wire frame is always larger than the original payload. That extra size is "overhead".

True or false: "You can replace Wi-Fi with Ethernet without touching your web browser."

True. That is the whole point of separation of concerns — swapping Layers 1/2 leaves Layer 7 untouched because each layer only talks to its neighbours through a fixed interface.

True or false: "The Physical layer understands MAC addresses so it knows which device to deliver to."

False. Layer 1 only pushes raw bits (voltages/light/radio); addressing and framing live one floor up at Layer 2. Physical is pure signalling, address-blind.

True or false: "Encryption in classic OSI belongs to the Application layer because HTTPS shows in the browser."

False. Classic OSI assigns encryption/compression/translation to Layer 6 (Presentation). The browser being Layer 7 is a feel-right trap; exam answer = Presentation.

True or false: "UDP data at Layer 4 is called a Segment."

False. TCP's PDU is a Segment; UDP's is a Datagram. Same layer, different names because they are different transport protocols.

Spot the error

Spot the error: "Routers operate at Layer 2 and switches at Layer 3."

Swapped. Switch = Layer 2 (MAC), Router = Layer 3 (IP). Memory hook: a Router Routes using IP, and IP lives at Layer 3.

Spot the error: "The Transport layer chooses the path packets take across the Internet."

Wrong layer. Routing (path selection across networks) is Layer 3 (Network). Transport is end-to-end logic — ports, reliability, flow control — and is oblivious to the route between networks.

Spot the error: "Layer 3 delivers data to the correct application on the destination machine."

Wrong job. Layer 3 gets a packet to the right machine (via IP). Getting it to the right process/application uses port numbers at Layer 4 (Transport) — e.g. port 443 for the browser, not email.

Spot the error: "PDU chain bottom-to-top is Bits → Packets → Frames → Segments → Data."

Frames and Packets are swapped. Correct order: Bits → Frames → Packets → Segments → Data ("Big Fat Pandas Sleep Deeply"). Frames (L2) sit below Packets (L3).

Spot the error: "OSI has 7 layers and TCP/IP has the exact same 7 layers."

Wrong count. TCP/IP has 4 (or 5) practical layers. OSI's Application + Presentation + Session collapse into TCP/IP's single Application layer.

Spot the error: "The Data Link layer uses IP addresses to reach the next device on the local link."

Wrong address. Layer 2 uses MAC addresses for node-to-node delivery on the same link; IP addresses are logical, Layer-3 addresses used to cross between networks.

Spot the error: "Session management (like resuming a failed download from 90%) happens at the Transport layer."

Wrong layer. Dialog control, checkpoints and session setup/teardown are Layer 5 (Session). Transport handles reliability/ports, not session checkpoints.

Why questions

Why does each layer add a header instead of one big header being written once at the top?

So each layer stays independent: it only needs its own control info and can be redesigned without knowing the others' internals. This is what lets you swap protocols at one layer without rewriting the rest.

Why do we need Layer 4 (Transport) if Layer 3 already gets data to the right machine?

Because a machine runs many programs at once. Layer 3 finds the host; Layer 4's port numbers steer the data to the specific process (browser vs email) on that host.

Why can't the Physical layer just handle everything — bits are all that really travel, right?

Raw bits carry no meaning: no way to know where one message ends, who sent it, or if it arrived intact. Higher layers add framing, addressing, and error checks so bits become organised, deliverable data.

Why is "overhead" unavoidable in networking?

Because encapsulation is additive — every layer prepends its own metadata (headers, an L2 trailer). The wire must carry payload plus all wrappers, so the frame is always bigger than the raw data.

Why does the receiver's stack run upward (de-encapsulation) rather than downward?

The sender wrapped the data outermost-last (Physical last); the receiver must unwrap in reverse — peel the outermost (frame) first, then packet, then segment — like opening nested boxes from the outside in.

Why do we teach OSI at all if the real Internet uses TCP/IP?

OSI's clean 7-layer split is the best vocabulary and mental model for reasoning about where a job belongs. Engineers still say "that's a Layer 3 problem" even when running TCP/IP.

Edge cases

Edge case: A ping travels from your PC to a server two networks away. At how many layers is a new MAC header applied along the way?

At every hop/link. MAC addresses are link-local, so each router rebuilds a fresh Layer-2 frame with new source/dest MACs per link — while the IP addresses (Layer 3) stay end-to-end.

Edge case: Two devices are on the same local switch — is any Layer-3 routing involved?

No. Same-network delivery is pure Layer 2: the switch forwards frames by MAC. A router (Layer 3) is only needed to move between different networks.

Edge case: You send a 0-byte application message. Does anything still go on the wire?

Yes. Even with empty payload, the layers still add their headers (and L2 trailer), so a non-trivial frame of pure overhead is transmitted — headers are not optional.

Edge case: A hub connects three PCs. What OSI layer does a hub operate at, and why does it not read addresses?

Layer 1 (Physical). A hub just repeats electrical signals to all ports; it has no notion of MAC or IP, so it can't filter — it's address-blind by design.

Edge case: TLS in real TCP/IP sits between Transport and Application, but the exam asks "which OSI layer does encryption?" — what do you answer?

Layer 6 (Presentation). In classic OSI, translation/encryption/compression are Presentation's job; note the real-world TLS placement but give the OSI answer.

Edge case: If Layer 2 already does error detection (CRC), why can data still arrive corrupted at the application?

Because L2's CRC only checks one link and merely detects/drops bad frames — it doesn't guarantee end-to-end delivery. True end-to-end reliability (retransmission) is Layer 4 TCP, which UDP skips.