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
CCNA AI and Network Operations Practice Question
Drag and drop the following steps into the correct order to troubleshoot an end-to-end connectivity issue using a bottom-up approach.
⚠ Common exam trap
A common mistake is to begin with tools like ping before confirming physical and IP configuration; always validate lower layers first.
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
✓
Check physical layer connectivity and interface status
The correct troubleshooting order follows the OSI model bottom-up: start with physical connectivity (A), then verify Layer 3 addressing (B), use diagnostic tools (C) to isolate the failure, and finally implement the solution and verify restoration (D). Skipping layers can lead to misdiagnosis.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Check physical layer connectivity and interface status
Why this is correct
The first step in any network troubleshooting is to validate the physical layer; checking cable connections, transceiver presence, and interface state (up/up) rules out Layer 1 faults that invalidate all upper-layer logic. Use show interfaces and show ip interface brief to identify a down/administratively down port, CRC errors, or duplex mismatch. If the link is down, no higher-layer configuration can deliver packets, making this the proper starting point.
- ✓
Verify IP addressing and default gateway configuration
Why this is correct
With Layer 1 confirmed, the next logical check is Layer 3 addressing; verify the host's IP address, subnet mask, and default gateway consistency. On routers, examine show ip route for the connected and static routes so the source and destination are in known subnets. An incorrect gateway or overlapping subnet can cause traffic to be sent to a non-existent router, leading to timeouts even though the physical link and interface are healthy.
- ✓
Use ping and traceroute to isolate the failure point
Why this is correct
Ping and traceroute are the correct tools to isolate where packets are dropped after address validation; a ping to the local gateway succeeds while pinging the remote host fails, which reveals a routing or ACL issue upstream. Traceroute displays each hop, exposing routing loops, silent ACL drops, or devices that fail to return ICMP messages. Extended ping with a specific source interface isolates multi-homed router behavior, ensuring the test uses the intended path.
- ✓
Resolve the issue and verify full connectivity restoration
Why this is correct
Once the cause is identified, applying the correction is incomplete without end-to-end verification; reconfigure the interface, ACL, or routing entry and then ping to the final destination from the original source. Also check interface counters and device logs for recursive errors or new issues. This final validation confirms the entire path, not just a single segment, and is essential for closing the troubleshooting loop.
Quick reference
OSI Model Reference
| Layer | Name | PDU | Key Protocols / Devices |
|---|---|---|---|
| 7 | Application | Data | HTTP, HTTPS, DNS, SMTP, FTP, SSH |
| 6 | Presentation | Data | TLS / SSL, JPEG, ASCII encoding |
| 5 | Session | Data | NetBIOS, RPC, SIP |
| 4 | Transport | Segment / Datagram | TCP, UDP |
| 3 | Network | Packet | IP, ICMP, OSPF — Routers |
| 2 | Data Link | Frame | Ethernet, Wi-Fi, PPP — Switches, Bridges |
| 1 | Physical | Bits | Cables, NICs, Hubs, Repeaters |
Go deeper
Related to this question
Learn chapter
Generative AI Prompting for Network Tasks
Key term
OSI model
The OSI model is a conceptual framework that standardizes the functions of a telecommunication or computing system into seven distinct layers, from physical hardware to application software.
Key term
CAN
A CAN (Controller Area Network) is a robust vehicle bus standard designed to allow microcontrollers and devices to communicate with each other without a host computer.
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.