5 exercises — choose the best-structured answer to common Network Engineer interview questions. Focus on protocol precision, OSI layer reasoning, and hands-on troubleshooting methodology.
How to answer network engineering questions in interviews
Start with the OSI layer: ground your answer — is this L2, L3, or L4?
Name the mechanism: don't just say "TCP is reliable" — mention ACKs, sequence numbers, retransmissions
Show decision logic: when do you use this? when don't you? what are the trade-offs?
Command + interpretation: mention the diagnostic command AND what the output means
0 / 5 completed
1 / 5
The interviewer asks: "Can you explain what BGP is and when you would use it?" Which answer is most technically precise?
Option A is the strongest: it defines BGP → explains autonomous systems with ASN → names the routing attribute types (AS-PATH, MED, LOCAL_PREF) that make BGP different from metric-based protocols → gives three practical use cases including cloud connectivity. Option C is technically excellent: contrasts BGP against IGPs (OSPF, EIGRP) and correctly categorises the attribute-based traffic engineering — this is a strong answer for a networking interview. Option D is accurate and practical but lacks the technical depth of AS/ASN/attributes. Option B is correct but superficial. Key vocabulary to demonstrate: AS, ASN, path attributes vs metrics, exterior vs interior gateway protocol, multi-homing.
2 / 5
The interviewer asks: "What's the difference between TCP and UDP, and how do you decide which to use?" Choose the most complete answer.
Option A is the strongest: it identifies the OSI layer first, then details each protocol's mechanisms (handshake, sequence numbers, ACKs, retransmissions vs none), frames the decision as loss vs latency tolerance, and gives specific protocol examples for each choice — including the key insight that a retransmission arrives too late to be useful for real-time media. Option D is also strong — correctly identifies statefulness, overhead, and the continuous media use case with "occasional loss acceptable." Option C is accurate but brief. Option B is too simple. Interviewers want to see: three-way handshake, sequence numbers/ACKs, the latency vs reliability trade-off, and concrete protocol examples (HTTP, DNS, VoIP).
3 / 5
The interviewer asks: "What is a VLAN and why would you use one?" Which answer shows the deepest understanding?
Option A is the strongest: full definition (Layer 2 → logical segment → broadcast domain partition), explains the inter-VLAN routing requirement clearly, and provides three well-named use cases with the reasoning behind each (compromise containment, flood minimisation, functional grouping). Option C adds the important 802.1Q/trunk link detail — a valid technical depth signal. Option D is practical and accurate — production/dev/IoT examples are real-world scenarios. Option B is accurate but too brief. Key terms to demonstrate: broadcast domain, Layer 2, Layer 3 routing, trunk ports, 802.1Q tagging.
4 / 5
The interviewer asks: "Can you walk me through the OSI model and explain where common networking issues occur?" Which answer is most useful in practice?
Option A is the strongest: gives the full 7-layer model with real-world examples at each layer, explains the bottom-up troubleshooting methodology, names specific failure modes at each critical layer (carpet/cable → spanning tree → routing/ACL → port/firewall/service), and ends with the practical heuristic (most issues are L3 and L4) plus the diagnostic commands. Option D is excellent — correctly names tools per layer (ping for L3, telnet/nc for L4) — a strong signal of hands-on experience. Option C is accurate but generic. Option B's mnemonic alone is not sufficient. What interviewers want to hear: a bottom-up troubleshooting methodology, specific failure modes at each layer, and the tools you use to diagnose them.
5 / 5
The interviewer asks: "We're troubleshooting a network issue where a host can ping a server but cannot establish a TCP connection to port 443. Walk me through your diagnosis." Choose the best structured answer.
Option A is the strongest: it starts by interpreting the ping result (Layer 3 confirmed), names the Layer 4 failure hypothesis, then gives five ordered diagnostic steps with specific commands at each step, and ends with the critical packet-level interpretation — RST means refused, no response means dropped. This command+interpretation pairing signals real hands-on experience. Option D has the same diagnostic steps but in slightly less structured form and lacks the RST vs drop interpretation. Option C correctly identifies the RST vs timeout distinction — a key diagnostic insight. Option B is accurate but shallow — 'telnet times out' does not distinguish server firewall from network ACL. The RST vs no-response distinction (refused vs dropped) is what interviewers use to filter candidates who've actually captured packets from those who only read documentation.