17.8.5 Module Quiz - Build A Small Network: Exact Answer & Steps

Ever tried to pull together a tiny LAN just for a class quiz and ended up with a tangle of cables, IP conflicts, and a router that refuses to boot?
That feeling is all too familiar for anyone who’s ever been handed “Module 17.8.5 – Build a Small Network” and told “you have 30 minutes, go!” The good news? You don’t need a PhD in networking to ace that quiz. You just need a clear mental map, a few proven steps, and a habit of checking the obvious before you panic Nothing fancy..

Below is the full‑stack guide that walks you through exactly what the 17.5 module expects, why each piece matters, and the shortcuts most students miss. 8.Grab a notebook, fire up your simulator (Packet Tracer, GNS3, or even a real‑world lab), and let’s get that small network humming.

What Is the 17.8.5 Module Quiz?

In plain English, the 17.8.5 quiz is a hands‑on assessment that asks you to design, configure, and verify a basic LAN/WAN topology using a handful of devices: a router, a switch, two PCs, and sometimes a server.

• IP addressing basics (subnetting a /24 into /30 or /28 blocks)
• Device inter‑connection (crossover vs straight‑through, though most simulators hide that)
• Basic Cisco IOS commands for interface setup, routing, and verification

You won’t be writing OSPF or BGP here. Think of it as the “bread‑and‑butter” of networking: get the IPs right, enable the interfaces, and ping across the wire.

The Typical Lab Layout

PC1 ---- Switch ---- Router ---- Switch ---- PC2
                |                     |
               Server (optional)    |

• Router: One FastEthernet (or GigabitEthernet) interface facing each switch.
• Switches: Usually just a Layer 2 device; no VLANs unless the quiz adds a “guest” network.
• PCs: Static IPs (or DHCP if the quiz explicitly asks for it).
• Server: Often a DNS or web server, used for a final “ping to 8.8.8.8” style test.

That’s the short version. The real trick is how you get each device talking.

Why It Matters / Why People Care

If you’ve ever been stuck in a help‑desk role, you know the pain of a mis‑configured subnet. A single wrong octet can break connectivity for an entire floor. The 17.Practically speaking, 8. 5 quiz trains you to spot those errors before they become tickets Simple, but easy to overlook..

• Confidence in the lab – Once you nail this, moving on to VLANs, ACLs, or routing protocols feels less intimidating.
• Job‑ready skill – Employers love candidates who can “wire up a small network and prove it works” without needing a script.
• Exam safety net – In larger certification exams (CCNA, CompTIA Network+), a similar scenario pops up. Knowing the 17.8.5 steps saves you minutes and reduces anxiety.

In practice, the ability to verify your work (ping, traceroute, show ip interface brief) is worth more than memorizing command syntax. Real‑world networking is all about confirming that the packet actually left the box.

How It Works (Step‑by‑Step)

Below is the meat of the guide. Follow each block exactly, and you’ll have a functional network before the timer hits zero.

1. Sketch the Topology First

Before you even launch Packet Tracer, grab a scrap of paper. Draw the two switches, the router in the middle, and the end devices. Label each interface:

• Router‑G0/0 → Switch‑A (LAN)
• Router‑G0/1 → Switch‑B (WAN)

Why? Practically speaking, a visual reference stops you from plugging a PC into the wrong port later. Trust me, that “oh‑no‑I‑wired‑the‑router‑to‑my‑PC” moment hurts And that's really what it comes down to..

2. Assign IP Addressing Scheme

Most instructors give you a /24 block, like 192.This leads to 168. In practice, 10. 0/24.

Tip: If the quiz asks for a /30 point‑to‑point link, just carve out a tiny subnet (e.g., 10.0.0.0/30). Most students forget to change the mask on the router’s second interface, and the ping fails instantly Nothing fancy..

3. Build the Physical Connections

In the simulator:

1. Drag a Router (e.g., 2811) onto the canvas.
2. Add two Switches (2960 is common).
3. Place two PCs and optionally a Server.
4. Use copper straight‑through cables from each PC to its nearest switch.
5. Connect the router’s Gig0/0 to Switch‑A, and Gig0/1 to Switch‑B.

If you’re on real gear, remember that modern routers have auto‑MDI/MDIX, so a straight‑through cable works both ways. Still, double‑check the LEDs; a solid green means link, a blinking orange means traffic.

4. Configure the Router Interfaces

Open the CLI of the router and type:

enable
configure terminal
interface gigabitEthernet0/0
 ip address 192.168.10.1 255.255.255.0
 no shutdown
exit
interface gigabitEthernet0/1
 ip address 192.168.20.1 255.255.255.0
 no shutdown
exit
exit
write memory

Why no shutdown? Newer IOS defaults interfaces to “administratively down.” Forgetting that line leaves the port dead, and your PCs will never see a link Simple as that..

5. Set Static IPs on the End Devices

On PC1 (in Packet Tracer, click the PC → Desktop → IP Configuration):

• IP Address: 192.168.10.2
• Subnet Mask: 255.255.255.0 (auto‑filled)
• Default Gateway: 192.168.10.1

Do the same on PC2 with its 192.168.And 20. So 2 address and gateway 192. Plus, 168. Think about it: 20. And 1. Which means if you have a server, give it the 192. 168.20.10 address.

6. Verify Layer‑2 Connectivity

Before you test routing, make sure each PC can see its own switch:

• On PC1, open the Command Prompt and type ping 192.168.10.1.
• If you get replies, the LAN side is good.
• Do the same on PC2 (ping 192.168.20.1).

If a ping fails, check the cable colors, the interface status (show ip interface brief on the router), and the PC’s IP config.

7. Test Inter‑Network Routing

Now the real magic: can PC1 talk to PC2?

On PC1, run:

ping 192.168.20.2

You should see a series of replies. If not:

1. Verify the router’s routing table with show ip route. Both directly connected networks should appear as C 192.168.10.0/24 and C 192.168.20.0/24.
2. Confirm that no ACLs are blocking traffic (the quiz rarely adds them, but a stray access-list line can ruin everything).
3. Double‑check that you didn’t accidentally enable ip proxy‑arp on one interface and not the other—unnecessary for this lab but can cause confusion.

8. Optional: Add a Simple DHCP Server

If the quiz asks for DHCP, you can enable it on the router:

ip dhcp pool LAN
 network 192.168.10.0 255.255.255.0
 default-router 192.168.10.1
exit
ip dhcp excluded-address 192.168.10.1 192.168.10.10

Then set the PCs to “DHCP” instead of static IPs and verify they receive an address in the correct range.

9. Save Your Work

Never leave a lab unsaved. In IOS, write memory (or copy running-config startup-config) writes the config to NVRAM. And in the simulator, hit File → Save. A quick habit that saves you from a “I lost my config” panic.

Common Mistakes / What Most People Get Wrong

The most frequent “why won’t it ping?” moment is a mismatched subnet mask. One PC thinks it’s on a /24, the router’s interface is /30—suddenly the packet never leaves the host Worth knowing..

Practical Tips / What Actually Works

1. Label everything in the simulator – Right‑click a device → “Rename.” A name like R1-G0/0-LAN saves you from guessing later.
2. Use show ip interface brief constantly – It’s the fastest way to see which interfaces are up and what IP they hold.
3. make use of the “ping –t” command – Continuous ping helps you spot intermittent link flaps while you tweak cables.
4. Keep a small cheat‑sheet – A one‑page list of the most used commands (conf t, int, ip address, no shut, write mem).
5. Practice “fail fast” – Intentionally break a link, then fix it. The muscle memory of re‑adding a cable beats reading the manual under pressure.
6. If the quiz allows it, use a VLAN – Some instructors throw in a single VLAN ID to see if you can configure switchport access vlan 10. It’s easy: conf t → interface range fa0/1‑24 → switchport mode access → switchport access vlan 10.
7. Don’t over‑engineer – Adding routing protocols, ACLs, or NAT when the prompt only asks for static routing is a recipe for point‑loss. Simplicity wins.

FAQ

Q: Do I need to configure a DNS server for the quiz?
A: Only if the instructions explicitly mention name resolution. Otherwise, DNS is unnecessary; a plain ping to an IP address is enough.

Q: What’s the difference between a crossover and a straight‑through cable in this lab?
A: Modern devices have auto‑MDI/MDIX, so a straight‑through works for router‑to‑switch and PC‑to‑switch links. Use a crossover only if you’re on legacy hardware without auto‑MDI/MDIX Worth keeping that in mind..

Q: Can I use DHCP on the router instead of static IPs?
A: Yes, but you must create a DHCP pool and exclude the router’s own address. The quiz will usually tell you which method to use.

Q: How do I verify that the router is actually routing, not just bridging?
A: Run show ip route. You should see both directly connected networks listed as C. If you only see one, the other interface is down or mis‑configured.

Q: My PC can’t ping the router, but the router can ping the PC. What’s wrong?
A: Check the PC’s default gateway and subnet mask. A common pitfall is a typo in the gateway address, causing the PC to send traffic to the wrong next hop.

Building a tiny network for the 17.8.This leads to 5 module isn’t rocket science; it’s a matter of order, verification, and a little attention to detail. Consider this: sketch, assign, connect, configure, then ping—repeat until every device replies. Keep those common slip‑ups in mind, and you’ll breeze through the quiz, leaving more mental bandwidth for the next lab.

Now go fire up your simulator, follow the steps, and watch those green LEDs light up. And you’ve got this. Happy networking!