CompTIA A+ 220-1101: Internet Connection Types, Network Types, and Key Features Explained
Introduction: Start with the Path, Not the Panic
One of the easiest ways to lose time in support is to mix up internet connection types, local network types, and performance terms. A user says, “The internet is down,” but that could mean the ISP link failed, the Wi‑Fi signal is weak, the router is misconfigured, DNS is failing, or only one device has a bad IP configuration. For CompTIA A+ Core 1, you need to compare these terms cleanly and recognize them in scenario questions.
The key distinction is this: an ISP connection type is how a site reaches the provider, while a network type describes the scope or purpose of the network itself. In a lot of homes, you’ll see fiber coming in from the ISP, a wired LAN for the desktop, and a WLAN for the phones and laptops that need to move around without being tied to a cable. A branch office usually has its own LAN and WLAN for the people on-site, and then a WAN link back to headquarters so the whole place stays connected as one environment. That’s the part folks miss sometimes: each layer has its own failure point, so the troubleshooting approach changes with it.
What the A+ Exam Expects You to Compare
For this objective, I usually split everything into four buckets so the terminology doesn’t all run together in your head.
- Internet connection types: DSL, cable, fiber, satellite, fixed wireless, cellular/mobile broadband, and legacy references like dial-up and ISDN.
- Network types by scope or purpose: PAN, LAN, WLAN, CAN, MAN, WAN, and specialized networks such as SAN.
- Access scope and architecture: intranet, extranet, internet, client-server, and peer-to-peer.
- Features and behavior: bandwidth, throughput, latency, jitter, packet loss, availability, reliability, symmetric vs asymmetric service, and metered vs unmetered usage.
Common exam traps are predictable: internet vs Wi‑Fi, WAN vs internet, bandwidth vs throughput, and router vs modem vs ONT vs gateway.
Internet Connection Types
An internet connection type is basically the medium and service you use to get to your provider. That choice has a big effect on speed, latency, mobility, cost, and even what gear you’d expect to find on-site.
| Connection type | Medium | Typical traits | Common hardware | Best fit | Main drawback |
|---|---|---|---|---|---|
| DSL | Telephone copper | Distance-sensitive, usually lower speed | DSL modem/router | Basic home use where newer service is unavailable | Loop distance and line quality reduce performance |
| Cable | Coaxial cable | Good speeds, shared access network | DOCSIS cable modem or gateway | Home and small office broadband | Congestion can reduce real throughput |
| Fiber | Optical fiber | High speed, low latency, often strong upload performance | ONT plus router/gateway | Remote work, business, heavy cloud use | Availability varies |
| Satellite | Radio via satellite | Broad rural reach, variable latency by orbit type | Dish, modem/CPE, router | Remote locations | Weather, obstruction, latency, and plan limits |
| Fixed wireless | Radio from provider site | Can be good in rural areas, location-sensitive | Outdoor antenna/CPE, often PoE-powered, router | Rural homes and small sites | Path quality and interference matter |
| Cellular/mobile broadband | LTE/5G radio network | Mobile and flexible, highly variable | Phone, hotspot, mobile router | Travel, temporary access, failover | Signal variability, throttling, metered plans |
Connection Types in More Practical Detail
DSL uses telephone copper and is still worth knowing because it appears in older neighborhoods and exam questions. Common variants include ADSL and VDSL. The exam takeaway is simple: DSL performance depends heavily on copper quality and distance from the provider equipment. In older setups, DSL and voice service can coexist on the same line with filters or splitters. Some DSL services use PPPoE authentication, so a router may need a username and password on the WAN interface. If a DSL user has sync issues, line stats such as attenuation and SNR margin can point to a poor-quality loop.
Cable internet runs over coax and typically uses DOCSIS. A+ does not require deep DOCSIS engineering, but you should recognize that newer DOCSIS versions generally support better performance and efficiency than older ones. Cable modems register with the provider and are provisioned for a service tier. Real-world support often involves checking the modem status page for downstream/upstream lock, channel bonding, and signal levels. Cable is not automatically “slow at night,” but shared-node congestion can reduce throughput during busy periods.
Fiber usually means FTTH/FTTP service, often delivered over GPON or similar provider technologies. In many fiber deployments, an ONT provides the customer handoff to Ethernet, though some business or provider-managed installations use integrated optical CPE instead of a separate standalone ONT. Fiber usually offers the best combination of speed and latency, and many plans are symmetric, though not all are. A common support point is checking ONT status lights such as power, optical/PON, and alarm/LOS.
Satellite matters because it reaches places wired broadband may not. GEO satellite typically has very high latency because of orbital distance, while LEO systems usually have much lower latency, though still affected by coverage, congestion, handoffs, and local sky visibility. Practical issues include dish alignment, weather fade, snow or debris on equipment, and obstructions such as trees or buildings blocking the terminal’s view of the sky. Some satellite services also use carrier-managed addressing that can complicate inbound access.
Fixed wireless uses a radio link from a provider tower or nearby site to customer equipment. Many deployments prefer line-of-sight, but some can work in near-line-of-sight or limited non-line-of-sight conditions depending on frequency, spectrum, and equipment. Outdoor radios are often mounted high and powered by PoE. The usual troublemakers are misalignment, interference on unlicensed bands, trees filling in during the summer, and weather knocking the signal around. It is often a better latency choice than satellite when the path is clean.
Cellular/mobile broadband includes LTE, 5G, hotspot devices, and tethering. Performance can swing pretty hard depending on signal quality, carrier congestion, the device’s capabilities, which band it’s using, and the plan rules like throttling or deprioritization. A phone hotspot usually creates a small WLAN for clients, while USB or Bluetooth tethering can act more like a direct personal link. Cellular is excellent for mobility and backup connectivity, but less predictable than wired service.
Legacy references such as dial-up and ISDN are mostly historical. You just need to know them as older telephone-based access methods, not something people commonly deploy today.
How the Connection Is Configured
In support work, the medium is only part of the story. The WAN side of a router may be configured in several ways:
- DHCP: common for cable and many fiber services.
- PPPoE: seen on some DSL and fiber providers; requires credentials.
- Static IP: more common on business service where inbound services or stable addressing matter.
- DNS settings: may come from the ISP automatically or be set manually.
The router typically provides the default gateway for the local subnet, performs NAT, and often runs DHCP for local clients. A lot of ISP gateways bundle the modem or ONT handoff, router, switch, and wireless functions into one box, which is convenient until you need to isolate a problem. Those devices may run in router mode or bridge mode. Bridge mode basically shuts off the routing and NAT functions so another router farther downstream can do that job instead. If both devices perform NAT, you can end up with double NAT, which can break gaming, VPNs, port forwarding, or inbound services.
ISP Path vs Local Network Path
This is the distinction students need to lock in:
I like to picture the path like this: client to AP or switch, then to the router, then to the modem or ONT or CPE, and from there out to the ISP and on to the internet or cloud service.
If the break happens between the client and the AP, that’s a local WLAN problem, not an ISP outage. If the client reaches the router but not the ISP, that is a WAN/provider path issue. If the client reaches public IPs but not websites by name, that is often a DNS issue. This is why “the internet is slow” is not a useful diagnosis by itself.
Network Types, Access Scopes, and Architectures
Not every networking term belongs in the same category. For exam clarity, separate them like this.
| Category | Term | Meaning | Example |
|---|---|---|---|
| Scope-based network type | PAN | Very short-range personal network | Bluetooth headset to phone |
| Scope-based network type | LAN | Local network in a home, office, or site | Office Ethernet network |
| Scope-based network type | WLAN | A wireless LAN is just a local network that uses 802.11 Wi‑Fi for the wireless part. | Office Wi‑Fi SSID |
| Scope-based network type | CAN | Campus Area Network | University multi-building network |
| Scope-based network type | MAN | Metropolitan Area Network | City government network |
| Scope-based network type | WAN | Network spanning multiple locations | Branch to HQ connectivity |
| Specialized/private | SAN | Storage network for servers and storage | iSCSI or Fibre Channel fabric |
| Access scope | Intranet | Private internal organizational resources | Employee portal |
| Access scope | Extranet | Controlled access for outside partners | Vendor access portal |
| Access scope | Internet | Public global network | Public websites |
| Architecture | Client-server | Centralized services for clients | Domain login and file server |
| Architecture | Peer-to-peer | Devices share directly with each other | Small ad hoc file sharing |
LAN is your local site network. WLAN is the wireless access portion of that local network, usually based on IEEE 802.11 and commonly branded as Wi‑Fi. A WLAN is often bridged into the LAN, but it may also be segmented into separate SSIDs or VLANs for guest access, staff access, or device isolation.
WAN means the network spans distance. It is not automatically the internet. A WAN can be built a bunch of different ways, like leased lines, MPLS, Metro Ethernet, site-to-site VPN tunnels over the public internet, broadband links, or SD-WAN overlays. The internet is a public network, but a WAN can be private, public, or some mix of the two.
PAN is personal-range connectivity such as Bluetooth devices, NFC pairing, or a direct tether. Do not confuse a phone hotspot with PAN in every case: hotspot mode usually creates a small WLAN, while Bluetooth tethering is closer to PAN behavior.
SAN is a specialized storage network, not a general end-user network type in the same sense as LAN or WAN. It commonly uses Fibre Channel or iSCSI to connect servers to storage. If a SAN starts running into latency issues, the servers can feel slow even when the user LAN looks perfectly fine.
Intranet, extranet, and internet describe trust and access scope. Intranet resources stay within the organization. Extranet resources are private but shared with approved outside parties, often through VPNs, identity platforms, or reverse proxies. Internet resources are public.
Client-server and peer-to-peer are architectural models, not geographic network types. Client-server setups usually make centralized authentication, permissions, backups, and management much easier to handle. That centralization can really improve control and consistency, although security still depends on how well the whole thing’s implemented. Peer-to-peer is pretty simple in very small environments, but once you try to scale it up, things get messy fast.
Performance Features That Actually Affect User Experience
| Feature | Meaning | Why it matters |
|---|---|---|
| Bandwidth | Available data-carrying capacity of a link | Sets the ceiling for how much traffic can move |
| Throughput | Effective delivered data rate | Reflects real performance after overhead and congestion |
| Latency | Delay across the path | Critical for interactive apps |
| Jitter | Variation in latency | Causes choppy voice/video |
| Packet loss | Dropped packets are packets that either have to be resent or never make it back at all. | That’s the sort of problem that leads to buffering, robotic-sounding audio, freezing, and that all-around sluggish feeling people complain about. |
| Symmetric | Similar upload and download rates | Good for cloud backup, video calls, remote work |
| Asymmetric | Download faster than upload | Common in consumer broadband |
| Metered | Usage-limited service | Important for hotspots and some rural plans |
| Availability | Uptime/reachability over time | Tied to outage frequency and service expectations |
| Reliability | Consistency and stability of service | This is basically a measure of how often the service degrades or outright fails. |
Bandwidth is not the same as throughput. A link might be provisioned for 500 Mbps, but the user may only see 320 Mbps because of Wi‑Fi limits, congestion, protocol overhead, or a bottleneck on the endpoint itself. That is not always abnormal. And remember, a speed test only shows one path at one moment in time — it doesn’t tell you how every possible route across the internet behaves.
Latency, jitter, and packet loss often matter more than raw download speed for voice, gaming, remote desktop, and video meetings. A connection can have plenty of bandwidth and still feel terrible if packets are arriving late, unevenly, or not showing up at all.
Wi‑Fi link rate is also not the same as real throughput. A laptop might show a high negotiated wireless rate, but the real application throughput is usually lower because of overhead, interference, channel width, signal quality, and the way airtime gets shared with other devices.
Supporting Hardware and First Checks
| Service | Expected handoff device | Local distribution | Common first check |
|---|---|---|---|
| DSL | DSL modem | Router/AP/switch | DSL sync/status light |
| Cable | DOCSIS modem or gateway | Router/AP/switch | Online/downstream/upstream lights |
| Fiber | ONT or provider optical CPE | Router/AP/switch | PON/optical/alarm status |
| Fixed wireless | Outdoor CPE/radio | Router/AP/switch | Signal strength and alignment |
| Satellite | Dish and modem/CPE | Router/AP/switch | Obstruction, weather, and equipment status |
| Cellular | Phone, hotspot, or mobile router | WLAN, USB, or Bluetooth tether | Signal bars, data mode, plan status |
A router connects networks and usually serves as the local default gateway. A switch connects wired LAN devices. An access point provides WLAN access. A gateway can mean either the default gateway IP concept or a consumer all-in-one device, so read exam wording carefully.
Wireless Performance and Security Basics
Many “internet problems” are really WLAN problems. The big practical differences are:
- 2.4 GHz: longer range, lower throughput, more interference.
- 5 GHz: faster, shorter range, usually better for performance.
- 6 GHz: very high capacity where supported, shorter range, newer client support required.
Slow Wi‑Fi usually comes down to poor AP placement, overlapping channels, heavy interference, weak signal, or just too many clients fighting over the same airtime. In homes, central AP placement helps. In larger spaces, mesh Wi‑Fi can improve coverage, but wired backhaul is usually better than wireless backhaul when possible.
For security, prefer WPA3 where supported. If not available, use WPA2-AES/CCMP. And honestly, avoid WEP and WPA/TKIP altogether—they’re outdated and not worth keeping around. Change default router admin credentials, disable WPS if not needed, keep firmware updated, and isolate guest devices from business or trusted devices. In a small business, guest Wi‑Fi and POS traffic should be separated by SSID, VLAN, or both.
Performance and Troubleshooting Workflow
Use a layered process instead of guessing:
- Scope the issue: one device or all devices?
- Identify access type: wired, Wi‑Fi, hotspot, or tethering?
- Check local IP configuration: confirm IP, subnet, gateway, and DNS.
- Test the default gateway: if that fails, the issue is local.
- Test a public IP: if gateway works but public IP fails, suspect WAN/ISP.
- Test DNS: if public IP works but hostname fails, suspect DNS.
- Compare wired vs wireless: if wired is good and Wi‑Fi is bad, fix WLAN first.
- Check provider equipment: modem, ONT, CPE, hotspot status lights and logs.
- Check environmental factors: interference, weather, obstruction, congestion.
- Escalate to ISP: once the local path is verified.
Useful commands: ipconfig /all on Windows, ifconfig or ip addr on Linux, ping, tracert/traceroute, and nslookup or dig. A classic DNS symptom is this: pinging a public IP works, but browsing by hostname fails. That usually means the internet path exists but name resolution is broken.
| Symptom | Likely layer | Likely cause | First test |
|---|---|---|---|
| Only one Wi‑Fi device is slow | WLAN/client | Weak signal, interference, bad adapter | Compare near AP or on wired connection |
| All devices offline | WAN/provider or router | ISP outage, failed modem/ONT, router issue | Check gateway and ISP equipment lights |
| Can ping a public IP but not websites | DNS | Bad DNS server or resolver issue | nslookup a hostname |
| Calls are choppy but downloads seem fine | Performance | Jitter or packet loss | Ping test and compare latency variation |
| Uploads are painfully slow | Service characteristic or WLAN | Asymmetric plan, congestion, poor signal | Run a wired speed test and compare upload performance |
Practical Scenarios You Should Recognize
Home user: fiber internet, bad bedroom Wi‑Fi. The wired desktop tests fine, but the laptop in a far room drops calls. That is a WLAN coverage or interference problem, not a fiber outage.
Rural user: fixed wireless vs satellite. If the property has a clean path to a provider tower, fixed wireless often gives better latency than satellite. If tower coverage is poor and wired service does not exist, satellite may be the only practical option.
Small business: cable primary with LTE backup. The store uses cable for normal operation and a dual-WAN router for failover to cellular during outages. Card processing and email may continue during failover, but large downloads and guest Wi‑Fi performance may be reduced. That is business continuity, not luxury.
Remote worker: video meetings over home broadband. If video calls are poor, do not jump straight to “buy more bandwidth.” Check upload speed, latency, jitter, packet loss, Wi‑Fi signal, and whether the user is on a congested 2.4 GHz network.
Business vs Consumer Internet
| Feature | Consumer service | Business service |
|---|---|---|
| Support | Best effort | Often priority support |
| Service expectations | Usually limited | May include uptime and repair targets |
| Static IP options | Less common | More common |
| Failover planning | Less common | More common and operationally important |
| Cost | Lower | Higher |
Business service often justifies its cost when downtime affects POS, phones, cloud apps, or staff productivity. “Predictable performance” depends on the contract and service type, but business offerings commonly provide better support expectations and recovery commitments.
Exam Essentials and Wrong-Answer Traps
Memorize these distinctions:
- ISP connection type = how you reach the provider.
- Network type = scope or purpose of the network.
- Architecture = how services are organized.
- Performance metric = how the connection behaves.
If the question mentions X, think Y:
- Optical handoff device → ONT
- Short-range personal pairing → PAN
- Centralized authentication → client-server
- Remote rural availability → satellite or fixed wireless
- Mobile temporary access → cellular hotspot/tethering
- Private internal company portal → intranet
Wrong-answer traps:
- Wi‑Fi is not the ISP.
- A WAN is not automatically the internet.
- A router is not the same thing as a modem.
- A gateway device is not the same thing as the default gateway concept.
- High bandwidth does not guarantee low latency.
- Fiber service does not automatically mean strong Wi‑Fi.
Quick Command Practice
Windows: ipconfig /all, ping, tracert, nslookup
Linux/macOS: ip addr or ifconfig, ping, traceroute, dig or nslookup
Use them in order: verify local addressing, test the gateway, test a public IP, then test a hostname.
Conclusion
For A+ Core 1, keep the categories straight. DSL, cable, fiber, satellite, fixed wireless, and cellular are internet connection types. PAN, LAN, WLAN, CAN, MAN, and WAN are scope-based network types. SAN is specialized storage networking. Intranet, extranet, and internet describe access scope, and client-server and peer-to-peer describe architecture.
When troubleshooting, separate the local path from the provider path, and separate throughput from latency, jitter, and packet loss. That mindset helps on the exam and in the real world. If you identify the category first, most “compare and contrast” questions become much easier to solve.