A VLAN divides a physical switch into logical networks, keeping Layer 2 broadcasts within their own group of ports. Learn how 802.1Q trunk links carry VLAN traffic, how VLANs differ from IP subnets, and why communication between them needs inter-VLAN routing through a router or Layer 3 switch.

Multiple Choice

What term describes the logical segmentation of a switch into separate broadcast domains?

VLAN stands for Virtual Local Area Network, and it creates separate broadcast domains on a switch by grouping ports into logical networks. When devices are placed in the same VLAN, they share broadcasts and can communicate directly at Layer 2, but broadcasts from one VLAN never reach devices in another VLAN. This separation is done without changing physical connections, using VLAN tagging (like 802.1Q) on trunk links and placing each switch port into a specific VLAN. To have devices in different VLANs talk to each other, inter-VLAN routing (via a router or a Layer 3 switch) is required. This is distinct from IP subnets (which are network-layer boundaries) and from the broader notion of a broadcast domain or a collision domain, which VLANs define and isolate at Layer 2 within a single physical switch.

A single Ethernet switch can connect dozens or hundreds of devices, but that doesn’t mean every device needs to share one local network. Virtual local area networks, or VLANs, let network teams split a switch into separate logical groups. Each group forms its own Layer 2 broadcast domain, even when its devices use the same physical hardware.

That separation matters more than it might seem. It helps contain network traffic, supports clearer security boundaries, and gives administrators room to organize devices by role rather than by the switch they happen to plug into.

One switch, several logical networks

Imagine a school with computers in classrooms, office staff devices, and wireless access points. If every connected device belongs to the same Layer 2 network, a broadcast sent by one device may be received by many others. Some broadcasts are necessary for network communication, but too many can create noise and waste bandwidth.

A VLAN divides that shared physical network into smaller logical groups. Ports assigned to one VLAN belong to the same broadcast domain. A broadcast from a device in that group stays within it; devices in another VLAN don’t receive it.

The physical layout doesn’t have to change. A computer in Room 12 and a printer in the main office might connect to the same switch, yet belong to different VLANs. Conversely, devices on different switches can share a VLAN if the switches are connected and configured to carry that VLAN’s traffic.

That’s the key idea: VLANs organize network traffic by configuration, not by where a cable runs.

What happens when a device sends a broadcast?

At Layer 2 of the network model, Ethernet devices use MAC addresses to send frames across a local network. When a device needs to reach a local destination but doesn’t yet know its MAC address, it may send a broadcast frame. The switch forwards that frame to other ports in the same VLAN, but not to ports assigned to different VLANs.

This boundary is called a broadcast domain. A VLAN creates a separate one on the switch. The terms are closely linked, but they aren’t interchangeable: a broadcast domain describes the area a Layer 2 broadcast can reach, while a VLAN is a way to create and manage that area.

Think of a switch as a large building with several departments. The building is shared, but internal mail for one department doesn’t automatically land on every desk. VLANs provide that kind of separation for network traffic.

How switches keep VLANs apart

For a device connected directly to a switch, the port is commonly configured as an access port. An access port belongs to one VLAN, and the connected device usually doesn’t need to know that VLANs exist. It simply sends and receives ordinary Ethernet frames.

Links between switches often need to carry traffic for several VLANs at once. These are known as trunk links. A trunk typically uses IEEE 802.1Q tagging: the switch adds a small identifier to a frame to indicate which VLAN it belongs to. The receiving switch reads the tag and keeps the traffic in the right logical group.

When traffic leaves a trunk for an access port, the switch removes the tag before sending the frame to the end device. In most common setups, laptops, printers, and servers don’t handle these tags themselves. The switches do the sorting behind the scenes.

Careful configuration matters here. If two switches disagree about which VLAN a tag represents—or a trunk doesn’t carry a needed VLAN—devices may lose connectivity. It’s a small detail with a very visible result: one team can’t reach a printer, or an access point stops passing a wireless network.

VLANs and IP subnets: related, but not identical

A VLAN operates at Layer 2, the data-link layer. An IP subnet operates at Layer 3, the network layer. These concepts often work together, but they describe different things.

Many networks assign one IP subnet to each VLAN. For example, a staff VLAN might use one range of IP addresses, while a guest VLAN uses another. That arrangement makes traffic easier to route and manage. Still, a VLAN doesn’t automatically equal a subnet; they’re separate configurations, and their relationship depends on the network design.

The distinction becomes especially important when devices in different VLANs need to communicate. Because each VLAN is its own Layer 2 broadcast domain, a device in one VLAN can’t simply send a local Ethernet frame to a device in another. The traffic needs a Layer 3 device to route it.

That job may fall to a router or a Layer 3 switch. This process is called inter-VLAN routing. Network administrators can then set rules for which groups may communicate. For instance, staff devices might reach an internal file server, while guest devices can reach the internet but not internal systems.

VLANs help with more than traffic control

VLANs can make a network easier to manage. A company might group devices by department, function, or security needs: staff computers in one VLAN, voice phones in another, and guest Wi-Fi in a third. If someone moves to a different desk, the port can be assigned to the appropriate VLAN without rewiring the building.

They can also help limit the reach of certain threats or misconfigurations. A broadcast storm in one VLAN, for example, is less likely to spread across every other VLAN. Separating guest traffic from business systems can reduce exposure, too.

But VLANs aren’t a complete security solution. They create separation at Layer 2; they don’t automatically filter all traffic or prevent every attack. If two VLANs need strict isolation, administrators also need suitable routing rules, firewalls, and access controls. A locked door is useful, but someone still has to decide who gets the key.

Don’t confuse VLANs with collision domains

A collision domain is another Layer 2 term, but it refers to a different kind of boundary. It describes the part of a network where devices’ transmissions could collide if they send at the same time. Modern switched Ethernet generally gives each switch port its own collision domain, and full-duplex links avoid collisions in normal operation.

A VLAN, by contrast, separates broadcast traffic. One switch can have many collision domains—often one per active port—and several broadcast domains, one for each VLAN. The terms describe different aspects of how traffic behaves.

This distinction is useful when troubleshooting. A broadcast that reaches devices it shouldn’t may point to a VLAN or trunk configuration issue. A link that repeatedly drops or performs poorly may have a different cause, such as a bad cable, mismatched speed settings, or a duplex problem.

A clear boundary makes a better network

VLANs let network teams divide shared switching equipment into distinct Layer 2 networks. Access ports place connected devices into a VLAN; trunk links carry tagged traffic between network devices; and Layer 3 routing allows selected communication between VLANs.

The result is a network that can be organized without being tied to physical walls or cable paths. Used thoughtfully, VLANs reduce unnecessary broadcast traffic and make it easier to separate groups of devices. They’re not a substitute for routing policy or security controls, but they provide a useful foundation for both.

A switch may look like one box in a rack. With VLANs, though, it can serve several well-separated networks at once.