HomeField notes
PACKETDOJO GUIDES

Network troubleshooting interview questions

A practical network interview gives you a symptom and asks you to reason with incomplete evidence.

Ask for the missing context

Which users are affected? Which service? When did it last work? Does the same destination work from another source? These answers narrow the investigation before you touch configuration.

Make each command earn its place

Say what your observation would support or rule out. A route lookup answers a different question from a service-specific packet probe.

Explain the blast radius

Propose a small change, a rollback, and a verification plan. Restoring one flow is incomplete if the fix disrupts another team or removes a security boundary.

PUT THE IDEA TO WORK

The missing way home

Austin service network. Independent north and south core paths connect the ingress and egress routers. Requests reach both service networks, but the second client subnet cannot receive replies. The first client subnet still works. Investigate the two service networks from R1: 10.201.224.0/24 to 10.201.234.0/24 (TCP/443), and 10.201.225.0/24 to 10.201.235.0/24 (TCP/8443).

Network topology6 devices 6 links

The missing way home — network topologyR1: Client edge. R2: Ingress. R3: North core. R4: South core. R5: Egress. R6: Service gateway. R1 connects to R2. R2 connects to R3. R2 connects to R4. R3 connects to R5. R4 connects to R5. R5 connects to R6. Connections show physical links, not service health.R1 ↔ R2 · 10.201.240.0/30R2 ↔ R3 · 10.201.241.0/30R2 ↔ R4 · 10.201.242.0/30R3 ↔ R5 · 10.201.243.0/30R4 ↔ R5 · 10.201.244.0/30R5 ↔ R6 · 10.201.245.0/30R1Client edgeR1 · Client edgeR2IngressR2 · IngressR3North coreR3 · North coreR4South coreR4 · South coreR5EgressR5 · EgressR6ServicegatewayR6 · Service gateway
Physical links · Service health not shown

Free to practice. No account required.

Create an account to save your results and build your skill graph.