Study Switching Technologies, VLANs & Layer 2 Design for Network+ (N10-009)
Use VLANs, trunks, interface settings, spanning tree, MTU, and jumbo-frame concepts correctly in switching scenarios.
Switching questions are rarely just about vocabulary. They are usually about segmentation, loop avoidance, port role, or a user group that can no longer reach what it should. CompTIA is testing whether you can recognize when the real issue is Layer 2 behavior before you waste time blaming routing or DNS.
STP: Spanning Tree Protocol, the family of mechanisms used to prevent Layer 2 loops in switched networks.
Trunk: A switch port that carries traffic for multiple VLANs rather than just one access VLAN.
What CompTIA is really testing
Strong switching answers usually depend on one of these distinctions:
- access port versus trunk port
- VLAN membership versus inter-VLAN routing
- loop-prevention issue versus broadcast-domain issue
- frame-size problem versus reachability problem
The Layer 2 choices that matter most
| If the question is really about… | Protect this idea first |
|---|---|
| one department cannot reach its own resources | VLAN assignment or trunk carry list |
| all users experience unstable connectivity after a link change | loop prevention and STP |
| big storage transfers fail strangely but small traffic works | MTU or jumbo-frame mismatch |
| one port should only serve one endpoint role | access-port behavior and port-security thinking |
Keep these boundaries clear
| Concept | What it does | What it does not do by itself |
|---|---|---|
| VLAN | separates Layer 2 broadcast domains | route between those domains |
| trunk | carries multiple VLANs across one link | decide policy between VLANs |
| STP | prevents Layer 2 loops | fix bad VLAN design |
| jumbo frame / MTU | changes maximum frame size | solve congestion by itself |
A practical switch-state reading example
1Port Gi1/0/24
2Mode: trunk
3Allowed VLANs: 10,20,30
4Native VLAN: 1
5
6Port Gi1/0/12
7Mode: access
8Access VLAN: 20
What to notice:
- the access port serves one VLAN
- the trunk carries several VLANs between switches or between a switch and another network device
- if VLAN 20 users fail only across the uplink, the trunk is a better suspect than the access port
Common traps
- assuming a VLAN problem is automatically a routing problem
- forgetting that both ends of a trunk must agree on the intended behavior
- treating STP like optional overhead instead of loop protection
- assuming MTU issues look exactly like a full outage
What strong answers usually do
- ask which VLAN the host should be in before touching anything else
- decide whether the path crosses a trunk or stays local
- keep loop prevention separate from gateway or routing logic
- remember that Layer 2 failures often affect one user group or one segment first, not everyone equally
Quiz
Continue with 2.3 Wireless Devices, Channels & WLAN Design to keep building the implementation layer.