Servers, Switches, and Cables — The Hardware Zoo

Hyperscaler Network Engineer · Module 1: Data Centers from Zero

Lesson 4 of 8

Foundations⏱ 30 min

Prerequisites: What Is a Data Center, Really?, Racks, Power, and Cooling — The Physical World

What you'll be able to do: Tell a server, a switch, and a router apart by their jobs, and pick the right cable — copper, DAC, or fiber — for any link by distance and speed.

If servers are the workers, switches are the traffic cops at every intersection, and cables are the roads connecting them. That is the whole zoo in one sentence — but the devil is in the details: a cable that is too long, too slow, or built for the wrong job turns a fast computer into one that might as well be shouting across a canyon. And this is not a rare edge case. Every rack on earth is wired with dozens of cables, and picking the wrong one for a link is one of the most common and expensive beginner mistakes. Today you learn to see the zoo like an engineer: which box does the thinking, which box directs the traffic, and which cable belongs on which road — short hop, long hallway, or across the street.

Here's the puzzle.

Scenario. You're wiring a new row of racks. The parts cage hands you a bin of cables — copper, DAC, fiber — and a work order with four links. Each link lists its distance and speed. One of these links is a trap: the obvious pick is wrong, and a senior engineer is watching to see if you catch it.

Given artifacts. The four link exhibits (diagram below — hover each card for details):

Link 1: server → top-of-rack switch, same rack, 3 m, 100G.
Link 2: rack row A → rack row B, 80 m, 100G.
Link 3: building 1 → building 2, 2 km, 100G.
Link 4: aggregation switch → core switch, 10 m, 25G.

Your task: For each of the four links, name the cable type — copper, DAC, or fiber (and for fiber, which kind: short-reach or long-reach) — plus a one-line reason; then call out which link is the trap and explain why the obvious pick fails there.

Workspace (analyze-and-answer): Four rows — one cable pick plus one-line reason per link — and a trap callout box. The page records your answers when you hit Commit; nothing is graded.

Hint ladder:

Hint 1 — where to look

Sort the links by distance first — shortest to longest. Cable families line up with distance bands: arm's-length, across the room, across the campus. Which band does each link fall in?

Hint 2 — what to compare

For each link, ask two questions: can the signal survive the distance, and is there a cheaper option that also survives? The cheapest survivor wins. Now look at Link 4 again — what does "cheapest survivor" assume about copper at 25G?

Hint 3 — the mechanism

Copper's reach shrinks as speed climbs — a copper cable that's perfectly fine at 3 meters can be deaf at 10 meters once the speed is high. The trap link is the one where the distance looks "short enough for copper" but the speed says otherwise.

Commitment ritual: When you have thought it through, check the box:

[ ] I've attempted this challenge and thought it through.

Checking it reveals the worked answer in S7. (Honor system — the page hides the answer until you commit.)

Your answer — optional, commit to a guess I've attempted this challenge and thought it through.

Checking the box reveals the worked answer in S7 below. Returning learners stay unlocked.

Servers: the workers

A server (in plain English: a computer whose job is to serve others — running apps, storing files, answering requests) does the thinking in the data center. Your laptop is a computer that serves you; a server is a computer that serves thousands of yous at once. Every cable in the building ultimately exists to get messages to and from servers. On the server's end, each cable plugs into a NIC — a network interface card (in plain English: the server's front door for cables — the socket where the network physically connects). No NIC, no conversation.

Why this matters for the challenge: the shortest hop on the work order starts at a server's NIC — the most ordinary link in the building, and the one where the cheapest cable wins.

Switches and routers: the traffic cops

If servers are the workers, something has to direct the traffic between them. A switch (in plain English: a box that connects devices in one place and forwards messages between them — the traffic cop at the intersection) looks at each incoming message and sends it out the right cable. The most common one you'll meet is the top-of-rack switch (in plain English: the switch sitting at the top of each rack that every server in that rack plugs into — the local intersection for one rack). A router (in plain English: a bigger-picture director that connects whole networks or buildings together — it decides which road out of town a message takes) operates one level up: switches handle the neighborhood, routers handle the highways between neighborhoods.

Why this matters for the challenge: every link in the work order runs between these boxes — knowing which box is which tells you what kind of road each link needs.

Copper: cheap, simple, short

The simplest road is copper — ordinary electrical cable carrying electrical signals, the same basic idea as the wiring in your walls. It's cheap, familiar, and easy to work with. Its weakness is physics: the electrical signal weakens as it travels, and it weakens faster at higher speeds — pushing more data per second means each pulse of signal is shorter and more fragile. So copper owns the short, slower links and surrenders as distance or speed climbs. Think of shouting: fine across a room, useless across a canyon.

Why this matters for the challenge: copper's home turf is the shortest hop on the work order — but "short" means something different at 100G than at 25G, so keep the distance bands in mind, not a single number.

DAC: copper without the middleman

A DAC — a direct attach cable (in plain English: a copper cable with the plugs permanently attached at the factory — no separate plug-in modules needed) — is copper optimized for the data center. Normal fiber links need a small plug-in module at each end to convert signals; a DAC skips those entirely, which makes it the cheapest per-link option at short range. DACs are the default inside a rack: a few meters, plug and go. But they're still copper, so the same physics applies — and the reach gets shorter as the speed climbs.

Why this matters for the challenge: DAC is the "cheapest survivor" for arm's-length links — the question is always where arm's-length ends at a given speed.

Fiber: light for the long haul

When copper runs out of breath, fiber-optic cable (in plain English: hair-thin strands of glass carrying pulses of light instead of electricity) takes over. Light doesn't fade the way electrical signals do, and it's immune to electrical noise — so fiber spans rooms, buildings, and cities. Each end needs a transceiver (in plain English: a small plug-in module that converts the server's electrical signals into light and back — one per end of the cable). Fiber comes in two flavors: multimode fiber (in plain English: short-reach fiber for tens to a few hundred meters — row to row, the economical choice at building scale) and single-mode fiber (in plain English: long-reach fiber for kilometers — building to building and beyond, the only glass that spans real distance).

Why this matters for the challenge: two of the four links sit beyond copper's reach in different distance bands — match the band to the fiber flavor, and save the exact reasoning for the worked answer.

Speeds and lanes: what 100G means

Cable shopping always involves a speed number: port speed (in plain English: how fast a plug can talk, measured in gigabits per second — 1G, 25G, 100G, 400G). Here's the twist: a fast port is usually built from multiple slower lanes (in plain English: parallel sub-channels inside one cable — a 100G link is often four 25G lanes side by side, like a four-lane highway). The mechanism that ties this lesson together: higher speed means a more fragile signal, and a more fragile signal means copper's reach shrinks. Distance and speed negotiate every link, and copper loses the negotiation first.

Why this matters for the challenge: this is the physics behind the trap — one link's distance looks innocent until you check what the speed does to copper's reach.

⏸ Pause animation

Step 1 of 5: Server A builds a packet — a small parcel of data with a destination address on it.
Step 2 of 5: The packet travels the cable (blue dot) from Server A's NIC to the switch.
Step 3 of 5: The switch flashes: it reads the address and picks the right outgoing cable — the traffic-cop moment.
Step 4 of 5: The packet continues along the second cable and arrives at Server B.
Step 5 of 5: Server B replies (red dot), and the whole trip runs in reverse — a conversation, one packet at a time.

🔒 The worked answer is hidden until you commit...

🔒 Revealed after the commitment ritual in S2 — attempt the challenge first. (Honor system: the page hides this until you check the box.)

Link 1 — 3 m, 100G, in-rack: passive DAC. The cheapest survivor wins, and at arm's length nothing beats a DAC: no transceivers to buy, plug and go, and 3 m is comfortably inside copper's reach even at 100G. One-line reason: cheapest per link at this distance, and the signal easily survives 3 m.

Link 2 — 80 m, 100G, row to row: multimode fiber with short-reach transceivers. 80 m is far beyond anything copper can do, so it's fiber — but which flavor? Short-reach (multimode) glass comfortably covers tens to ~100 m at a fraction of long-reach cost. One-line reason: beyond copper's reach, yet well inside short-reach fiber's band — so buy the cheaper glass.

Link 3 — 2 km, 100G, building to building: single-mode fiber with long-reach transceivers. Only long-reach glass spans kilometers; multimode's light scatters too far by a few hundred meters. One-line reason: kilometers demand single-mode — it's the only fiber whose light stays clean that far.

Link 4 — 10 m, 25G: THE TRAP. The obvious pick is a passive DAC — it's the in-rack standard, and "10 m" sounds short. But passive copper's signal fades after roughly 5 m at 25G speeds, so a 10 m passive DAC is deaf: the link would flap and die under load. The correct pick is active DAC (copper with built-in signal boosting) or multimode fiber with short-reach transceivers. One-line reason: at 25G, 10 m exceeds passive copper's reach, so the signal needs powered copper or light.

Wrong turns, named. On Link 1, you might have picked fiber "to be safe" — safe, but you'd buy two transceivers to solve a problem copper already solves; safety isn't free. On Link 2, you might have picked single-mode "because fiber is fiber" — it would work, but you'd pay for kilometers of reach to cross a room. On Link 3, the same "fiber is fiber" instinct kills the link: multimode glass dies at a few hundred meters, so the buildings would be dark. And on Link 4, the trap: "we always use DAC for short links" — true at 3 m, false at 10 m once the speed climbs, because distance and speed negotiate together and copper loses first.

Verify it worked: For each link, run three checks: reach ≥ distance (passive DAC ~7 m max, less as speed climbs; multimode ~100 m; single-mode kilometers), speed supported by the cable, and cheapest option that qualifies. If a cheaper option qualifies, you overpaid; if none qualifies, you picked wrong. All four links should now have exactly one cheapest survivor.

Servers think, switches direct, routers choose between networks — tell hardware apart by its job, not its shape.
Match the cable to the distance band: DAC inside the rack (a few meters), multimode fiber across the room (tens of meters), single-mode fiber across the campus (kilometers).
Copper is cheapest, but its reach shrinks as speed climbs — always check distance and speed together, never distance alone.
Fiber needs a transceiver at each end to turn electricity into light, and that extra cost is why you don't burn fiber on a 3-meter hop.
A fast port is built from slower lanes side by side (100G is often 4×25G) — so the speed on the box doesn't tell you which cable to buy until you know the distance.

Next: What Is a Network, Really? — You can now tell every box and cable apart by its job — next comes the invisible part: what actually travels across those cables, how a message finds its way from your phone to a server, and why "fast" turns out to mean two different things.