Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4
5Step 5
6Step 6
CCNA Network Infrastructure and Connectivity Practice Question
Drag and drop the following steps into the correct order to troubleshoot a Windows client that is unable to reach a remote server.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Run ipconfig /all to check IP configuration, subnet mask, default gateway, and DNS servers.
The correct troubleshooting order starts with verifying the client's IP configuration using ipconfig /all (A) to ensure the device has proper addressing. Next, test the TCP/IP stack by pinging the loopback address 127.0.0.1 (B). Then, ping the client's own IP address (C) to confirm the network interface card is operational. After that, ping the default gateway (D) to verify local network connectivity. If successful, ping the remote server (E) to test end-to-end connectivity. If that fails, use tracert (F) to identify where the path breaks. This bottom-up approach isolates the problem starting from the local host outwards.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Run ipconfig /all to check IP configuration, subnet mask, default gateway, and DNS servers.
Why this is correct
Running ipconfig /all is the foundational command to confirm the host's Layer 3 parameters: IP address, subnet mask, default gateway, and DNS servers. It also reveals whether the address was obtained via DHCP or is static, and can immediately expose APIPA (169.254.x.x) addresses that indicate a DHCP failure. Without this step, you cannot know if the client even has a valid configuration before testing further.
- ✓
Ping 127.0.0.1 (localhost) to test the TCP/IP stack.
Why this is correct
Pinging 127.0.0.1, the loopback address, isolates and verifies the local TCP/IP protocol stack at the network layer. A successful reply proves that IP, ICMP, and the protocol stack are installed and functioning on the host itself, regardless of the NIC or cabling. Because this test never sends packets onto the physical wire, a failure here indicates a corrupted or misconfigured TCP/IP stack.
- ✓
Ping the client's own IP address to verify the network interface card and IP configuration.
Why this is correct
Pinging the client's own IP address validates that the network interface card is bound to the correct IP address and that the NIC can process incoming and outgoing packets. A successful reply confirms the NIC driver is active and the IP configuration is properly assigned to the interface, while a failure after a successful loopback ping suggests a NIC or driver problem. This step also verifies the subnet mask is correct because the host determines whether its own address is local before generating the ICMP reply.
- ✓
Ping the default gateway's IP address to confirm local network connectivity.
Why this is correct
Pinging the default gateway's IP address confirms that the client can reach its local subnet's router, verifying Layer 2 connectivity and the IP configuration's consistency with the local network. A successful gateway ping proves the NIC, cabling, switch, and VLAN configuration are working for the local segment. If this ping fails but pinging the client's own IP succeeds, the issue is likely with the cable, switch port, or the gateway itself.
- ✓
Ping the remote server's IP address to test end-to-end connectivity.
Why this is correct
Pinging the remote server's IP address tests end-to-end connectivity across the entire network path, from the client's NIC to the remote host's interface. A successful reply proves Layer 3 routing works across all intermediate networks and that both hosts are reachable over IP. If this fails while the default gateway ping succeeds, the problem lies beyond the local subnet, requiring further path analysis.
- ✓
Use tracert to the remote server IP to determine the point of failure if the ping fails.
Why this is correct
Tracert (or traceroute) is used after a remote ping fails to identify the exact hop along the network path where the loss occurs, such as a router with no route or a filtered firewall ACL. It sends packets with incrementally increasing TTL values to elicit ICMP Time Exceeded responses from each router, mapping the path to the destination. This helps distinguish between a local network issue, an ISP outage, and a problem on the remote server's network.
Go deeper
Related to this question
Learn chapter
IPv4 Addressing and Address Classes
Key term
Interface
An interface is a point of connection or interaction between two systems, devices, or software components that allows them to exchange information or signals.
Key term
TCP
TCP is a connection-oriented transport layer protocol that ensures reliable, ordered, and error-checked delivery of data between applications over IP networks.
About these practice questions
This 200-301 question is part of Courseiva's 1,389-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-301 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 200-301 exam.