Compare and Contrast Common Networking Hardware for CompTIA A+ Core 1 (220-1101)

Why networking hardware matters so much on CompTIA A+ Core 1

On the A+ Core 1 exam, you’re not being asked to design a campus network from scratch. Honestly, it’s much more about spotting the device, knowing what role it plays, where it sits in the path, and what to check when something goes sideways. You’ve really got to know what a device does, where it belongs in the network flow, what people usually mix it up with, and what kind of symptoms tend to point your finger at it. Seems simple enough at first, right? Then the exam goes and tosses modem, gateway, router, switch, access point, and patch panel into the same scenario, and that’s usually where people start doubting every answer they know.

The easiest way to stay grounded is to follow the path the traffic’s trying to take and ask what that device is actually supposed to do. So anyway, I’d ask myself a pretty simple question: what’s this device actually doing? Is it connecting a device to the network, moving traffic around inside the LAN, sending traffic to another network, handing off service from the ISP, providing Wi-Fi, filtering traffic, or just keeping the cabling neat and tidy? Honestly, that one habit clears up a ton of the compare-and-contrast confusion.

The basic network path and exam mindset

When I’m sketching out a simple home network in my head, it usually looks something like this:

ISP → modem or ONT → router or gateway → switch or built-in LAN ports → access point or wireless clients

Now, in an office with structured cabling, I like to picture the path a little differently:

Endpoint → wall jack → in-wall horizontal cable → patch panel → patch cord → switch → router, firewall, or gateway → modem or ONT → ISP

That difference matters because a patch panel is just passive cabling infrastructure. It isn’t making traffic decisions or forwarding anything. It sits in the path, sure, but it doesn’t switch frames or route packets.

For A+, OSI references are simplified on purpose. Basically, the NIC is sitting right on that handoff between the physical side of the network and the data-link side. For A+, just think of switches as Layer 2 devices. Sure, some real-world models can do more, but for the exam, that’s the clean way to remember it. Routers are your Layer 3 devices. Access points primarily bridge wireless and wired Layer 2 traffic. Firewalls often filter at Layers 3 and 4, and newer next-generation firewalls may dig a little higher up the stack as well. Modems and ONTs are mostly about physical signaling, media conversion, and the provider handoff, so they don’t really fit neatly into just one clean OSI layer for exam purposes.

Core networking hardware you must compare and contrast

NICs: how endpoints join the network

A network interface card lets a device participate on a network. In exam terms, think of the NIC as the endpoint’s network hardware. It may be onboard, a PCIe add-in card, a USB Ethernet adapter, or a wireless adapter. Wired NICs commonly have link and activity LEDs; wireless adapters may not.

NICs use MAC addressing at Layer 2 and also deal with the physical signaling side of things. For Ethernet, know the common copper standards: 10BASE-T, 100BASE-TX, and 1000BASE-T. Usually, auto-negotiation handles speed and duplex for you, but when it doesn’t, or when a driver acts up, you can end up with mismatches and some truly ugly performance.

Typical NIC clues include one PC failing while others work, no link light on a known-good cable, a disabled adapter, a missing driver, or an APIPA address such as 169.254.x.x. APIPA usually means DHCP didn’t hand out an address on that interface, although isolation or some other misconfiguration can be part of the story too.

Windows examples are fair game for A+ troubleshooting:

ipconfig /all shows the address, gateway, DNS, and DHCP details. If you see a valid private address like 192.168.1.25 with a gateway like 192.168.1.1, the client at least has local addressing. If you see 169.254.44.10 and no default gateway, think DHCP failure, cable path, switch port, or NIC issue.

I’d also pop open Device Manager, check whether the adapter’s enabled and healthy, look at the negotiated link speed, and then move the machine to a different port to see if the problem follows the PC or stays with the jack. If the issue follows the machine around, that usually pushes the NIC or its driver pretty high on my suspect list. If it stays with the jack, suspect infrastructure.

Switches: the center of the LAN

A switch moves frames around inside the local network using MAC addresses. For A+, the safest way to think about switches is as Layer 2 devices. Some newer models do more than that, but you don’t need to overcomplicate it for the exam. For the exam, keep the picture simple: local traffic stays on the LAN, and the switch is the main place where PCs, printers, phones, and access points all come together.

A switch is an active device, so it needs power. Most of the time, you’ll see a row of Ethernet ports with little status LEDs next to them. Managed models may also include a console port, a management interface, SFP uplink slots, VLAN support, monitoring, and PoE controls. Unmanaged models are the simple plug-and-play kind.

At a basic level, the managed-switch features you should recognize are VLANs, access ports, trunk or uplink concepts, port statistics, and PoE management. You don’t need to configure those things for A+, but you should know why a business would bother with a managed switch in the first place.

Common switch symptoms include one dead port, one dead area, a failed uplink, loss of switch power, or lousy throughput caused by negotiation problems. If just one device is down, check the cable and the port right there first. If a whole floor is down, start thinking about switch power, the uplink, or the shared closet infrastructure.

People mix switches up with hubs and patch panels all the time. A hub is a classic Layer 1 multiport repeater that sends traffic to all ports. A switch forwards intelligently. A patch panel does not forward traffic at all.

Routers, gateways, and those all-in-one SOHO boxes

A router connects one network to another network. In a small network, that’s usually the default gateway — basically the first stop clients use when they need to leave the local network and head somewhere else. To be a little more precise, the default gateway is the router, or sometimes a Layer 3 interface, that hands traffic off when it needs to get out of the local subnet.

Routers are where several A+ concepts meet: NAT, DHCP, DNS forwarding, and often basic firewalling. NAT lets a whole pile of private LAN devices share one public WAN address. Private IP ranges such as 192.168.x.x, 10.x.x.x, and 172.16.x.x–172.31.x.x stay on the inside; the WAN side may have a public IP from the ISP.

On a typical home router, the single port labeled WAN or Internet faces the modem or ONT. The grouped LAN ports face your local devices. That physical distinction is a favorite exam clue.

A gateway is a broader term. In home networking, people often say “gateway” to mean an all-in-one ISP device that combines modem, router, switch, access point, NAT, DHCP, and firewall functions in one chassis. On the exam, read carefully because sometimes the question describes the function instead of actually naming the device.

Common router symptoms include local resources still working while internet access fails, missing or wrong default gateway settings, DHCP failures across multiple clients, double NAT problems when both the ISP gateway and a separate router are routing, or plain old misconfiguration in the management interface.

If a separate router sits behind an ISP gateway, bridge mode may be used on the ISP device so it stops doing routing and doesn’t create double NAT. That is a practical real-world issue and a useful distinction for A+ candidates.

Modems, ONTs, and provider handoff

A modem or ONT is the provider handoff device. Cable internet uses a cable modem with coax. DSL uses a DSL modem with an RJ-11 phone-style connection. Fiber service commonly uses an ONT, or optical network terminal, which converts the provider’s fiber service into Ethernet for customer equipment.

Users often call every ISP box a modem, but ONT is the more precise term in fiber environments. ONTs are commonly provider-managed and may require provisioning, authentication, or activation before service works.

Status lights matter here. Depending on device type, look for indicators such as power, downstream, upstream, online, PON, or LOS. If the LAN is fine but the online or PON status is bad, the issue is likely at the ISP handoff, not the switch on someone’s desk.

A sensible reboot order is usually modem or ONT first, then the router, then the switch or AP if you still need to keep going. But if the device has no sync, no online status, or a loss-of-signal light, you’re probably past the point of endless reboots and into ISP-escalation territory.

Access points and wireless hardware

An access point provides wireless clients access to the wired LAN. It advertises or hosts one or more SSIDs and bridges wireless traffic onto the network through its Ethernet uplink. APs commonly rely on upstream DHCP from the router or server; they usually do not act as the DHCP server unless they are part of an integrated wireless router or gateway.

Know the differences among common wireless devices:

• Access point: dedicated wireless access into the LAN
• Wireless router: router plus AP, often plus switch and firewall
• Mesh node: part of a coordinated multi-node wireless system
• Range extender/repeater: extends coverage, often with a throughput tradeoff
• Hotspot: temporary internet sharing, often from a phone or portable device

For the practical side of it, remember that 2.4 GHz usually gives you longer range but more interference, while 5 GHz usually gives you better throughput but a shorter range. And honestly, placement matters a lot here too. Try to avoid metal obstructions, microwave ovens, crowded utility closets, and tucked-away corners that can bury the signal. Ceiling or central placement is common in offices.

For security, WPA2 or WPA3 should be your expected answer. Weak or outdated wireless security is absolutely a red flag. If users can see the SSID but can’t authenticate, I’d usually be thinking wrong password, an encryption mismatch, or some kind of policy issue. If they can join Wi-Fi but still can’t reach anything, I’d start thinking about DHCP, the gateway, DNS, the AP uplink, or maybe even the ISP side of the path.

Firewalls, proxies, and the basic idea of traffic control

A firewall just filters traffic based on rules and policy. That’s really the core idea. Traditional firewalls usually make their decisions using IP address, port, and protocol information at Layers 3 and 4. Newer devices may also inspect application-layer traffic. A hardware firewall usually lives at the edge of the network, while a software firewall runs right on the endpoint itself.

Firewall symptoms are usually selective rather than total. If web browsing works but Remote Desktop won’t connect, I’d definitely suspect a firewall rule blocking TCP 3389. If ping doesn’t work but websites still load, ICMP may just be blocked somewhere in the path, and that’s not unusual. If one app breaks while everything else works, think policy before you think dead router.

A proxy is different: it acts as an intermediary for requests and may perform filtering, logging, or caching. For A+, I’d keep this memory trick in your back pocket: a router forwards traffic, a firewall filters traffic, and a proxy acts as the go-between.

Patch panels, cabling, and the passive side of the network

A patch panel is a passive termination point for the permanent cabling in the building. It belongs in structured cabling, not in the active traffic-forwarding path. In the closet, horizontal cable from office wall jacks terminates on the patch panel. Short patch cords connect the patch panel ports over to the switch ports.

Recognize related hardware: keystone jacks, punch-down blocks, patch cords, and horizontal cabling. At the A+ level, you should also know that T568A and T568B terminations need to stay consistent from one end of the cable to the other. The big rule is consistency on both ends for straight-through cabling in normal installations.

Patch panel problems usually show up as dead wall jacks, bad labels, incomplete punch-downs, or a jack that was never patched into a live switch port. A cable tester and a toner/probe are very useful tools here. If the wall jack label says Room 204-A, trace that label to the patch panel and then confirm that a patch cord actually connects it to a live switch port.

Legacy and additional A+ hardware to recognize

Legacy devices still show up in exam questions. A bridge is an older Layer 2 segmentation device; a switch is the modern multiport evolution. A repeater regenerates and retimes signals to extend reach. A hub is a classic Layer 1 multiport repeater that floods traffic to all ports.

Additional hardware categories worth recognizing:

• Media converter: converts one media type to another, such as copper Ethernet to fiber
• CSU/DSU: legacy WAN circuit termination hardware
• NAS: network-attached storage for shared files
• Powerline adapter: carries network traffic over building electrical wiring

They may not dominate the exam, but they’re still absolutely fair game for compare-and-contrast questions.

PoE: Power over Ethernet

PoE lets one Ethernet cable carry both data and power at the same time, and honestly, it’s one of those little things that makes installation a whole lot easier. You’ll usually see PoE used for access points, IP cameras, and VoIP phones. The standards you should recognize are 802.3af (PoE), 802.3at (PoE+), and 802.3bt (PoE++).

PoE can come from a PoE-capable switch, or from a midspan injector sitting between a non-PoE switch and the device that needs power. Troubleshooting PoE isn’t just about whether the port label says PoE. The switch also has a total power budget. A port might support PoE, but the switch may not have enough power budget left for every AP or camera that’s plugged in.

Typical symptoms include a ceiling AP that won’t power on, a phone that keeps rebooting, or a camera that works fine until more devices get added to the switch.

Troubleshooting by following the network path

Use this order:

1. Power — is the device on?
2. Link — are there link/activity LEDs or association status?
3. Local addressing — valid IP, mask, gateway, DNS?
4. Gateway reachability — can the client reach the local gateway?
5. Name resolution — is DNS the problem?
6. WAN/ISP — is the provider handoff healthy?

Three high-yield scenarios:

Wi-Fi connected, no internet: verify IP settings, ping the gateway, then test internet reachability and DNS. Just remember that failing to ping a public IP can be useful information, but some networks block external ICMP, so it’s not absolute proof all by itself.

One device down, others fine: think NIC, cable, wall jack, patching, or switch port. Move the device or the cable to a known-good port to narrow down where the fault is.

Whole area down: think shared switch, uplink, PoE source, closet power, or upstream router/firewall path.

Security and performance basics to keep in mind

For both the exam and real support work, the practical basics matter: change the default admin passwords on routers and APs, keep firmware up to date, use WPA2 or WPA3 for wireless, physically secure network closets, and be cautious about consumer all-in-one devices in business environments.

Performance clues matter too. A 100 Mbps link in an otherwise gigabit office can absolutely bottleneck users. Duplex mismatches can cause retries and terrible throughput. A badly placed AP can show strong signal in one room and poor performance in another because of interference and channel congestion. Wired links are still the preferred answer for stable high-throughput devices like desktops, printers, and uplinks.

Exam traps, memory aids, and Core 1 review

Most-missed distinctions:

• Modem/ONT vs router: ISP handoff versus network-to-network forwarding
• Router vs gateway: router is a device role; gateway may mean the default path off-net or an integrated ISP device
• Switch vs patch panel: active forwarding versus passive termination
• AP vs wireless router: wireless access only versus combined routing and Wi-Fi
• Firewall vs router: filtering versus forwarding
• Hub vs switch: flood all ports versus forward by MAC

If you see these clues, think this hardware:

• Coax → cable modem
• RJ-11 DSL line → DSL modem
• Fiber handoff → ONT or media converter context
• Single PoE ceiling device → access point
• No power cord, no LEDs, many ports in a rack → patch panel
• Separate WAN and LAN ports → router/gateway

A+ Core 1 hardware checklist:

• NIC
• Hub
• Switch
• Router
• Access point
• Modem
• ONT
• Firewall
• Patch panel
• Bridge
• Repeater
• PoE devices and injectors
• Gateway, proxy, NAS, CSU/DSU, media converter, extender/mesh node

What the exam is really testing is simple: can you identify the device by role, connectors, placement, and symptom pattern? If you can trace the path from endpoint to ISP and separate active devices from passive infrastructure, you will answer these questions much faster.

Conclusion

Networking hardware gets easier when you stop memorizing isolated definitions and start thinking in paths. NICs connect endpoints. Switches move local traffic. Routers and gateways move traffic between networks. Modems and ONTs hand off ISP service. Access points provide wireless access to the LAN. Firewalls filter. Patch panels organize cabling. Once those roles are clear, both A+ questions and real troubleshooting become much more manageable.