LAN vs WAN, Firewalls, and Latency: Network Basics for Project Managers

A LAN (local area network) connects computers, printers, and other devices within a single limited location — one office, one floor, one building — so they can share files, printers, and an internet connection. A WAN (wide area network) connects separate locations across long distances, such as linking a branch office back to headquarters in another city, typically over circuits leased from a telecom carrier or over the internet. Scope is the whole distinction: LAN is within a site, WAN is between sites.

What a LAN does

When a project opens a new office, the first networking deliverable is the LAN: switches, cabling, and Wi-Fi access points that let every device in the building reach every other device. Over that LAN, staff share a local printer, reach file servers, and hit the internet through a common gateway. LANs are owned and operated by the organization itself, run at high speeds (gigabit wired connections are the norm), and — because distances are short — deliver very low delay.

Devices worth recognizing at the LAN layer:

• Switch — connects devices within the LAN and forwards traffic between them.
• Wireless access point (WAP) — extends the LAN over Wi-Fi.
• Router — connects the LAN to other networks, including the WAN and the internet. The router is the boundary device: traffic leaving the building goes through it.

What a WAN does

The same new-office project has a second networking deliverable: connecting that office back to the rest of the company. That inter-site link — branch to headquarters, office to data center, site to cloud — is the WAN. Unlike a LAN, the organization usually doesn’t own the wires in between; it leases connectivity from a carrier (dedicated circuits such as MPLS, business broadband, or VPN tunnels over the public internet — a VPN, or virtual private network, is an encrypted tunnel across a network you don’t control).

WAN links are slower, more expensive per unit of bandwidth, and higher-delay than LAN connections, which is why WAN capacity is a genuine budget line and schedule dependency on multi-site projects: carrier circuit installation commonly has lead times measured in weeks or months, and it belongs on the critical path when a site opening depends on it.

Dimension	LAN	WAN
Scope	Single location (building, floor, campus)	Between locations across cities, countries, continents
Ownership	Organization owns the equipment	Carrier-provided circuits or internet links
Typical speed	High (gigabit and up)	Lower, and costlier per unit of bandwidth
Delay	Very low (short distances)	Higher, grows with distance
Example	Computers and printers sharing files in a new branch office	Linking that branch back to headquarters in another city
Project impact	Cabling, switches, Wi-Fi — install-phase work	Carrier lead times, recurring circuit costs, dependency on the critical path

Firewalls: rule-based traffic control

A firewall is the component that controls which network traffic is allowed to pass, based on configured rules. Rules typically specify direction (inbound or outbound), the port (a number identifying the service being reached, such as web or database traffic), and the source or destination network range. Well-run environments configure firewalls as default deny: everything is blocked unless a rule explicitly permits it.

The exam’s fingerprint for a firewall is exactly that pattern — a server that must accept inbound connections only on specific approved ports and only from trusted network ranges, with everything else blocked by default. No other standard infrastructure component does rule-based allow/block filtering; switches forward traffic, routers move it between networks, and load balancers distribute it.

For a project manager, firewalls show up as change requests and dependencies rather than as things you configure yourself. New applications need firewall rules opened before go-live; those rules go through security review; and a missed firewall request is a depressingly common cause of failed deployment nights. Put firewall-rule lead time into the plan the same way you’d plan any approval gate — and treat the security team as a stakeholder, not an obstacle (the project-facing side of this is covered in security basics for project managers).

Latency vs bandwidth: why fast connections still lag

Two different measures describe network performance, and PK0-005 expects you to keep them apart:

• Bandwidth is capacity — how much data can move per second. Think of it as the width of a pipe.
• Latency is delay — how long one packet takes to travel from source to destination, usually measured in milliseconds. Think of it as the length of the pipe.

A connection can have huge bandwidth and still feel terrible for real-time work, because interactive traffic cares about delay, not volume. The classic symptom: a globally distributed team whose video calls freeze and stutter on intercontinental calls even though everyone’s speed test shows plenty of download capacity. Speed tests measure bandwidth; the calls are suffering from latency. Distance is the dominant cause — data crossing an ocean traverses thousands of kilometers of fiber and many routing hops, and no bandwidth upgrade shortens that path. (A related term, jitter, means variation in latency from packet to packet — also poison for voice and video.)

The project-management takeaway: when planning anything real-time or interactive across geographies — video conferencing, remote desktops, a centralized application serving distant offices — ask about latency, not just bandwidth. This is also a hidden cost of centralizing infrastructure: consolidating servers into one site or region puts more users at WAN distance from their applications, a trade-off worth weighing alongside the availability arguments in eliminating single points of failure.

How the PK0-005 exam tests this

• A two-part scenario: devices sharing files and a printer within one new building, plus a link from that building back to headquarters in another city — and you must label the two connections respectively. Within-site = LAN, between-sites = WAN; watch the order the question asks for.
• A scenario where a server must accept inbound traffic only on approved ports from trusted ranges with everything else blocked by default, asking which component enforces this. Rule-based allow/block = firewall.
• A scenario where intercontinental video calls lag despite ample tested download speed, asking for the concept — distinct from bandwidth — that explains it. Delay over distance = latency.
• Distractor discrimination among network devices: switch (within the LAN), router (between networks), firewall (filters by rule), load balancer (distributes across servers). The verb in the scenario tells you which one it is.

Networking is one slice of the Basics of IT and Governance domain — the full PK0-005 study guide lays out every domain and how much each one weighs. Device-discrimination items reward repetition, and a bank of practice questions builds that reflex faster than rereading definitions.

Quick reference

• LAN = one location; devices share files, printers, and internet locally over organization-owned equipment.
• WAN = links separate sites across distance, usually over carrier circuits or VPN tunnels; slower, costlier, longer lead times.
• Router sits at the LAN/WAN boundary; switches and access points live inside the LAN.
• Firewall = rule-based traffic control: allowed ports and trusted sources in, everything else blocked (default deny).
• Firewall rule changes are go-live dependencies — build their approval lead time into the schedule.
• Bandwidth = capacity (pipe width); latency = delay (pipe length); jitter = variation in delay.
• High bandwidth cannot fix high latency — distance drives delay, which is what degrades intercontinental video calls.