Network Types

Network issues don’t fail the CompTIA A+ Core 1 exam by accident, they fail because the wrong network type gets matched to the wrong scenario. On the job, that same mistake can slow down troubleshooting, create bad tickets, or send you to the wrong team.

A network type is a plain label for what a network connects and how far it reaches. Objective 2.7 expects you to recognize these labels quickly and apply them in common support tasks.

In this guide, you’ll review six network types you’ll see on the exam and at the help desk: LAN, WAN, PAN, MAN, SAN, and WLAN. You’ll learn what each one is, where it’s used, and what keywords usually show up in CompTIA-style questions. By the end, you should be able to identify each network type from a short description, choose the right fit for a given use case, and avoid common mix-ups (like WLAN vs LAN, or SAN vs NAS).

Start with the basics: how to spot a network type in seconds

On the CompTIA A+ 220-1201 exam, you rarely get a full diagram. You get a short story, a few keywords, and a choice list that looks similar at a glance. The fastest way to choose the right network type is to use three clues in order: coverage area, purpose, and ownership. If you train yourself to spot those clues, most questions become simple matching.

Coverage area is the biggest clue (personal, local, metro, wide)

Start with distance and scope. Coverage area is the easiest signal because it shows up in everyday words like desk, building, campus, downtown, or across states. You do not need exact numbers. Plain ranges are enough to classify the network type in seconds.

Here is a practical way to think about scale:

PAN (Personal Area Network): A few feet around one person. Think of a phone connected to a smartwatch, earbuds, or a Bluetooth keyboard at a desk. If the devices feel like they belong to one user and move with them, that points to PAN.
LAN (Local Area Network): One room to one building, sometimes several buildings on the same site. A home network, a small office floor, or a school computer lab are classic LAN examples. If the description sounds like one organization wiring up a site, it is usually LAN.
WLAN (Wireless LAN): Same coverage idea as a LAN, but the access method is Wi-Fi. If you see “wireless access point,” “SSID,” or “connecting laptops over Wi-Fi in the office,” you are in WLAN territory. It is still local, it is just wireless.
MAN (Metropolitan Area Network): Several buildings across a city area. Think “connecting offices across downtown” or “linking multiple sites across a metro area.” If the story implies city-wide coverage but not cross-country, MAN is the best match.
WAN (Wide Area Network): Across regions, states, or countries. If the scenario mentions a headquarters connected to branch offices in other states, or links between distant sites, that strongly suggests WAN.

A quick mental picture helps: PAN is your desk and pockets, LAN/WLAN is your building, MAN is your city, WAN is beyond your city.

One caution for real life: names can overlap. A large campus network can blur the line between LAN and MAN, and a business can build private links that feel “WAN-like.” On the exam, use the standard meanings above and match the simplest fit to the scenario.

Purpose matters too: user traffic networks vs storage networks

Coverage area is not enough for every question. Some prompts describe a network that exists for a special job, not for general user browsing and email. This is where SAN stands apart.

Most network types in Objective 2.7 (LAN, WLAN, MAN, WAN, PAN) carry general data traffic. Users authenticate, open files, browse sites, join meetings, and print. These networks are built for mixed use.

A SAN (Storage Area Network) is different. It is built for block storage traffic between servers and storage systems. In plain terms, it is a dedicated network that lets servers talk to shared storage as if the storage were attached directly. The question stem often hints at this with phrases like “storage array,” “LUN,” “shared storage for virtualization hosts,” or “server-to-storage traffic.”

Separating storage traffic helps for a few concrete reasons that connect to troubleshooting:

Performance: Storage traffic can be heavy and steady. Keeping it off the user LAN reduces slowdowns during backups or large reads and writes.
Less congestion: When storage replication or backups run, you do not want office Wi-Fi or the wired LAN to feel “laggy.”
Easier control: A SAN is easier to lock down and monitor because it has a narrow purpose. If a storage link fails, you know where to look first.

For exam-style thinking, use this simple rule: if the network exists mainly to connect servers to storage, choose SAN even if the devices are in the same building.

Ownership and cost hints: private networks vs carrier networks

When a question includes words about billing, contracts, or external circuits, shift your focus to who owns the network. Ownership is a strong clue because it changes how the network is built, supported, and troubleshot.

In most workplaces, LAN and WLAN are privately owned. A home or business controls the switches, access points, cabling, and local routing. Troubleshooting often stays internal: check the switch port, confirm the SSID and password, replace a patch cable, or review VLAN settings.

Many WAN connections, on the other hand, involve a service provider. The company may own the routers on-site, but the long-distance link is often leased or managed by a carrier. CompTIA questions may hint at this with terms that suggest a provider service, such as:

MPLS (carrier-managed private routing between sites)
Metro Ethernet (often used to connect locations across a city area)
Dedicated fiber (a leased, high-capacity circuit)
Broadband VPN (site-to-site connectivity built over consumer or business internet access)

Ownership clues matter during triage. If only one office cannot reach headquarters, and the local LAN works, you may be dealing with a WAN circuit issue. That often changes the next step: gather circuit details, check the edge router status, then escalate to the provider if the local equipment looks healthy.

Keep one exam-safe reminder in mind: the internet is a WAN, because it spans large geographic areas and many networks. At the same time, not every WAN is the internet. A private MPLS network between branch offices is still a WAN, even if it never touches public internet routing.

LAN explained: the everyday network inside a home, school, or office

A LAN (Local Area Network) is the network you rely on when you connect devices inside a single site. It’s the “close to home” network that supports daily work, like logging in, printing, accessing shared files, and reaching the internet through a gateway. For CompTIA A+ (220-1201), the key is not memorizing a perfect size. The key is recognizing that a LAN stays local to one organization and one location, even if it is split into multiple logical segments.

A helpful mental model is a building’s plumbing. The pipes can branch into many rooms and floors, but the system is still the building’s plumbing. A LAN works the same way: it can be divided into parts for control and safety, but it still serves the same local site.

What a LAN connects and where it usually lives

A LAN connects end devices (PCs, laptops, printers, phones, IP cameras) and local resources (file servers, authentication systems, local apps) inside one location. In practical terms, “local” usually means one building, a home, a school, or a small campus under one team’s control.

That “one site” idea stays true even when the LAN is complex. Many real LANs include:

Multiple subnets: Separate IP networks, often used to reduce broadcast traffic and keep traffic organized.
VLANs (Virtual LANs): Logical separation at the switch level, often used to isolate departments (HR vs guest vs student lab) while still using the same physical switches.
Access methods: Wired Ethernet and Wi-Fi can both feed into the same LAN (Wi-Fi is the wireless access method, the LAN is the local network being joined).

This distinction matters for exam questions. A prompt might mention “VLAN 20” or “multiple subnets,” but if everything is still inside the same school or office site, it’s still a LAN.

A short scenario makes the scope clear. Imagine a help desk ticket: “Users on the 3rd floor can’t reach the file share or print, but the 1st and 2nd floors work.” That pattern points to a local switching problem, not a WAN outage. A likely cause is a failed access switch serving that floor (or its uplink). The network problem is contained to one part of the building, which is a classic LAN troubleshooting boundary.

Common LAN hardware and what each device does

Most LANs are built from a small set of devices that show up in both exam questions and real tickets. You don’t need deep configuration knowledge for A+ Objective 2.7, but you do need quick recognition.

A simple way to separate roles is to ask: “Does it connect devices, connect networks, or provide Wi-Fi?”

A switch connects devices within the LAN. It moves traffic inside the local network, usually based on MAC addresses. In an office, the switch is the reason desktops, printers, VoIP phones, and uplinks can all talk locally.
A router connects different networks. On a LAN, the router is often the default gateway that forwards traffic to other subnets and out to the WAN (often the internet). If a user can reach local printers but not websites, the router or WAN path becomes a suspect.
An access point (AP) provides Wi-Fi access into the LAN. Devices still join the LAN, they just enter over radio instead of copper. If Wi-Fi is down but wired desktops work, the AP, its power, or its uplink is a likely fault area.

LANs also depend on common network services. Two that appear often in A+ questions are:

DHCP: Automatically hands out IP settings (IP address, subnet mask, default gateway, DNS server). If DHCP fails, clients may self-assign an address and lose normal access.
DNS: Translates names into IP addresses. If DNS fails, users may say “the internet is down,” but some IP-based tests still work.

For ticket triage, this mental split helps: switches keep local traffic moving, routers move traffic between networks, and APs get wireless users onto the LAN.

LAN pros, limits, and common failures A+ might test

LANs are popular because they are fast and predictable. Inside one building, you control cabling, switch ports, and addressing. That control usually means high throughput, low latency, and fewer unknowns than the public internet. It also improves security, because access is managed by your organization.

The main limit is scope. A LAN doesn’t reach distant sites by itself. If a company needs connectivity between offices, it needs a WAN link (even if the WAN uses the public internet with a VPN). On the exam, if the story includes multiple sites in different cities, you have moved past LAN.

CompTIA A+ also expects you to recognize common LAN failures and connect them to symptoms. These issues are frequent because they sit close to the user.

Bad cable or bad termination: The link light may be off, the NIC shows “disconnected,” or the connection drops when the cable is moved. A user may report “it works sometimes.”
Wrong VLAN: The device connects, but it can’t reach the right resources. A common sign is getting an IP address from the “wrong” subnet (for example, a guest range instead of corporate). The user may have internet access but no internal shares, or the reverse.
Switch port disabled (administratively down): One desk goes dead after a move or change. The PC shows no link, and swapping the PC doesn’t help. Re-enabling the port or moving to a known-good port resolves it.
Duplex mismatch (briefly): The connection may come up, but performance is poor. Users report slow file copies, choppy VoIP, or many retransmits. This is less common on modern auto-negotiating gear, but it still appears in troubleshooting questions.
IP conflict: A user may get warnings about a duplicate IP, or the network works until another device comes online. You might see intermittent drops, failed pings, or one host knocking another offline.

A practical support habit is to separate local-only failures from routing or provider failures. If one floor, one room, or one group is down, suspect switching, VLAN, cabling, or DHCP scope issues. If local resources work but offsite services fail, suspect routing and WAN reachability. This approach matches how LAN issues show up in the real world and how A+ frames many of its network questions.

WLAN explained: a LAN that uses Wi‑Fi, with its own risks and rules

A WLAN (wireless local area network) is a LAN that users join over Wi‑Fi instead of an Ethernet cable. The coverage is still local, such as a home, office floor, or school building. What changes is the medium. Wireless uses radio signals, so performance and security depend on the air around you, not just the cable in the wall.

For CompTIA A+ (220-1201), treat WLAN as “LAN plus Wi‑Fi details.” If you see terms like SSID, access point, WPA2/WPA3, 2.4 GHz/5 GHz, or “weak signal,” you are in WLAN territory.