Basic Networking Quiz: Test Your Network Fundamentals Knowledge
True / False
Put in order
True / False
True / False
Put in order
Select all that apply
Put in order
Select all that apply
Disclaimer
This quiz is for educational purposes only. It does not replace official safety training, certification, or regulatory compliance programs.
Frequent Network Fundamentals Errors (OSI, Subnetting, DNS/DHCP, VLANs)
Mixing models instead of using them as troubleshooting shortcuts
A common miss is treating the OSI model and TCP/IP model as competing “right answers” rather than as two ways to localize a fault. Avoid this by practicing a single sentence diagnosis: symptom → layer → tool → next action (e.g., “Name resolution fails → Application/OSI L7 → nslookup → check DNS server and suffix”).
Subnetting math that ignores what the network actually needs
Learners often memorize formulas but forget the operational constraints: usable hosts, growth headroom, and summarization boundaries. Prevent errors by always writing: network address, first host, last host, broadcast before selecting a mask, and by confirming the default gateway belongs to the same subnet as the host.
Assuming “DNS is down” when it’s really client configuration
If users can reach an IP but not a hostname, the failure is usually DNS settings, search suffix, or split-horizon DNS expectations—not the web server. Verify what resolver the host is using and whether it can reach that resolver over the network path.
Confusing DHCP failure with “no internet”
A 169.254.x.x address (APIPA) indicates the host didn’t obtain a lease, not that the ISP is down. Troubleshoot in order: link state/VLAN assignment, then DHCP reachability (relay/helper, scope, or server availability).
Overtrusting segmentation and perimeter controls
VLANs reduce broadcasts; they don’t automatically enforce policy. Similarly, a firewall’s effect depends on its default policy and rule order. Treat segmentation as incomplete until you validate inter-VLAN routing and explicit allow/deny rules with a test flow.
Real-World Networking Decision Drills (Symptoms → Layer → Tool → Fix)
Use each prompt to practice the exact reasoning the quiz targets: identify the likely OSI layer, pick the fastest confirming tool, then name the smallest safe change.
Layer localization and tool choice
- “Connected, no network access”: A workstation shows link lights, but cannot ping its default gateway. What layer is most suspect, and what two checks do you perform before changing any switch configuration?
- “Ping by IP works, names fail”: Users can ping a public IP but cannot browse by hostname. What do you run to confirm resolver selection, and what configuration items commonly break in managed environments?
- “Only one application fails”: HTTPS works, but SSH to a management host times out. Which port/protocol pair do you verify end-to-end, and where could a policy silently block it (host, network, or perimeter)?
Subnetting and routing decisions
- New /27 branch subnet: You’re given 192.168.50.64/27. Determine the usable host range and the broadcast address, then decide what IP you would reserve for the default gateway and why.
- Inter-VLAN reachability: VLAN 10 and VLAN 20 exist, and clients can talk within their VLAN but not across. What Layer 3 component is missing, and what must be true about default gateways for both VLANs?
Wireless fundamentals under load
- Conference-room slowdown: Throughput collapses when the room fills. What are the two most likely 2.4 GHz problems to check (channel plan and airtime usage), and what simple change reduces co-channel interference?
Network Fundamentals Takeaways You Should Apply on the Job
- Translate every symptom into a layer and a tool. If you can’t name the OSI layer and the confirming command (ping, tracert, nslookup, arp, netstat), you’re troubleshooting by guesswork.
- Write the subnet boundaries before you pick an address. Always compute network, first/last host, and broadcast so you don’t assign an unusable IP or an out-of-scope gateway.
- Treat DHCP as a four-step exchange you can validate. When a host lands on APIPA, check link/VLAN first, then confirm the client can reach a DHCP server or relay path.
- Assume VLANs are about broadcast control, not security. If the requirement is “systems must not talk,” enforce it with ACLs/firewalls at the routing point—not by VLAN IDs alone.
- Verify ports and policies from both ends. Document the port/protocol for each service and confirm the effective firewall rule path (including default policy and rule order) before escalating.
Networking Fundamentals Glossary (With On-the-Job Examples)
- OSI model
- A 7-layer reference model used to localize where communication breaks. Example: “DNS lookups fail but IP pings succeed, so I’m focusing on OSI Layer 7 behavior and resolver settings.”
- TCP/IP model
- A practical 4–5 layer model that groups OSI functions into broader categories. Example: “This is an Internet-layer (IP) routing problem, not an Application-layer issue.”
- CIDR notation
- Slash-prefix representation of a subnet mask (e.g., /24). Example: “The printer is on 10.20.30.0/24, so 10.20.30.1–10.20.30.254 are host candidates.”
- Default gateway
- The router interface a host uses to reach non-local networks. Example: “The host can reach neighbors, but not external addresses—verify the default gateway is correct and reachable.”
- DNS (Domain Name System)
- Translates names to IP addresses (and other records) using queries to resolvers and authoritative servers. Example: “nslookup returns SERVFAIL, so I’m checking which DNS server the client is using.”
- DHCP (Dynamic Host Configuration Protocol)
- Assigns IP configuration (address, mask, gateway, DNS) via time-bound leases. Example: “A new VLAN needs a DHCP scope and possibly a relay/helper for clients to get addresses.”
- VLAN (Virtual LAN)
- Logical segmentation of Layer 2 broadcast domains on a switch. Example: “Accounting is VLAN 30; it reduces broadcast noise, but routing policies still decide who can reach what.”
- Trunk port
- A switch port that carries multiple VLANs using tagging (commonly 802.1Q). Example: “The AP needs a trunk to carry both the staff VLAN and the guest VLAN.”
- APIPA
- An automatic 169.254.x.x address assigned when DHCP fails, allowing limited local communication. Example: “If I see 169.254, I’ll validate the switchport VLAN and DHCP reachability before blaming the ISP.”
Authoritative References for Ports, DNS/DHCP, Firewalls, and Wi‑Fi
- IANA Service Name and Transport Protocol Port Number Registry — The official registry for well-known and registered ports; use it to verify port/protocol expectations during troubleshooting.
- IETF RFC 2131: Dynamic Host Configuration Protocol (DHCP) — The core specification for DHCPv4 behavior, including lease acquisition and renewal.
- ICANN: The Domain Name System (DNS) — A clear, authoritative overview of how DNS works and why resolvers and authoritative servers matter.
- NIST SP 800-41 Rev. 1: Guidelines on Firewalls and Firewall Policy — Practical guidance on firewall rule design, default policies, and operational management.
- NIST SP 800-153: Guidelines for Securing Wireless LANs (WLANs) — Foundational recommendations for wireless architecture and risk-aware configuration.
Basic Networking Quiz FAQ (OSI, Subnetting, DNS/DHCP, VLANs, Firewalls, Wi‑Fi)
Why does this quiz emphasize OSI layers if real networks use TCP/IP?
OSI is a troubleshooting map: it forces you to separate physical/link issues (cabling, VLAN tagging, duplex) from IP/routing problems and from application dependencies like DNS. TCP/IP describes how the stack is implemented; OSI helps you decide where to look first when symptoms are ambiguous.
What does a 169.254.x.x address mean during troubleshooting?
That’s APIPA—the host self-assigned an address because it did not obtain a DHCP lease. Treat it as a DHCP path problem until proven otherwise: confirm link/VLAN first, then confirm the DHCP server or relay path for that subnet.
If VLANs separate traffic, why can devices still talk across VLANs?
VLANs separate Layer 2 broadcast domains, but inter-VLAN communication is controlled at Layer 3. If a router or Layer 3 switch is routing between VLAN interfaces (SVIs), traffic can traverse VLANs unless you restrict it with ACLs or firewall rules.
Which ports should I know cold for firewall and connectivity questions?
Know the “default” ports for common admin and infrastructure services (e.g., DNS, DHCP, HTTP/HTTPS, SSH, RDP, SMTP) and be able to reason about direction (client-to-server) and protocol (TCP vs UDP). The quiz focuses on troubleshooting impact: what breaks when a port is blocked and how you confirm it.
How should I think about TCP vs UDP without memorizing a giant list?
Start with the requirement: reliability and ordering usually favor TCP; low latency and simple request/response often use UDP. Then validate by observing behavior (retransmissions, timeouts, application symptoms) rather than guessing. For deeper security context, pair this quiz with the Cybersecurity Basics Quiz.
Why do Wi‑Fi channels matter so much in 2.4 GHz troubleshooting?
In 2.4 GHz, many channels overlap, so an AP on a “non-standard” channel can create persistent interference and reduce throughput under load. A solid baseline is to use non-overlapping channel planning and then validate with a site survey and client performance tests. If policy requires user-safe access and auditability, the Employee Cybersecurity Knowledge Test complements the operational side of wireless deployments.
