CompTIA N10-009 Services, Routing, and Switching Issues Guide

This lesson is where many Network+ scenarios become multi-layer tickets. The link is up, but users still cannot reach what they need. CompTIA is testing whether you can separate switching, routing, and network-service failures instead of treating them as one generic connectivity problem.

Default gateway: The router a host uses to reach networks outside its local subnet.

Selective failure: A failure pattern where only certain users, VLANs, destinations, or services break, which usually means the issue is not at the broadest layer.

What CompTIA is really testing

The strongest answers usually come from asking:

• is the problem local, cross-subnet, or name-based
• is this a VLAN boundary problem or a gateway/path problem
• is DHCP, DNS, or routing the real missing dependency
• who is affected, and who is not

A fast symptom lens

Use a dependency-first view

    flowchart LR
	  A["Host config"] --> B["Local subnet and VLAN"]
	  B --> C["Default gateway and routed path"]
	  C --> D["Name resolution and app access"]

What to notice:

• if host config is wrong, later path checks can mislead you
• if local-subnet traffic works, the next question is usually gateway or upstream path, not random infrastructure change
• DNS matters after the path exists, not before

A practical command sequence

11. Check local IP, mask, gateway, and DNS settings
22. Ping the default gateway
33. Test local-subnet reachability
44. Test remote IP reachability
55. Test name resolution separately

What to notice:

• this sequence separates local path, routed path, and service dependency
• it stops you from calling everything “DNS” or everything “routing”
• many Network+ questions reward this exact separation

Small selective-failure example

1VLAN 30 users:
2- can ping local printer
3- cannot reach 10.20.40.20
4- can reach public websites by name

What to notice:

• the problem is selective, not universal
• DNS is probably fine because public websites resolve and load
• the stronger suspects are route, ACL, or segmentation policy toward one destination path

Common traps

• blaming DNS when the gateway or route is the real issue
• blaming routing when only one VLAN is not crossing a trunk correctly
• changing DHCP or DNS before checking the host configuration itself
• assuming a selective failure is a total-core outage

What strong answers usually do

• ask who is affected and who is not
• separate Layer 2 segmentation from Layer 3 pathing
• test direct-IP access and name-based access differently
• use the host configuration as evidence before changing infrastructure

Decision order that usually wins

Service and path failures become manageable when you separate local, routed, and named reachability. If local VLAN access works, suspect the gateway or routed path next. If IP works but hostname fails, suspect naming. If only one VLAN fails across a trunk after a change, suspect VLAN traversal or tagging. CompTIA often mixes these together to test whether you can isolate the failure layer cleanly.

Quiz

Continue with 5.4 Latency, Loss & Wireless when service and path failures feel easier to classify.