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
mediumDrag & DropObjective-mapped
XK0-006 Practice Question: Drag and drop the steps to troubleshoot a network…
Drag and drop the steps to troubleshoot a network connectivity issue using common commands in the correct order.
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
✓
Verify IP configuration (ip addr), check default gateway (ip route), test DNS resolution (nslookup), ping remote host (ping)
Troubleshooting network connectivity should follow a logical progression from local to remote: first verify your own IP address and subnet mask, then check the default gateway, then test DNS resolution, and finally test connectivity to a remote host. This systematic approach helps isolate the root cause efficiently.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Verify IP configuration (ip addr), check default gateway (ip route), test DNS resolution (nslookup), ping remote host (ping)
Why this is correct
This order follows the systematic troubleshooting methodology of starting from local configuration and progressing outward: first verify your own IP settings, then ensure routing is correct, then test DNS, and finally test end-to-end connectivity.
- ✗
Verify IP configuration (ip addr), test DNS resolution (nslookup), check default gateway (ip route), ping remote host (ping)
Why it's wrong here
This order is incorrect because DNS resolution should not be tested before verifying the default gateway. If the gateway is misconfigured, DNS queries will fail even if DNS servers are reachable.
- ✗
Ping remote host (ping), verify IP configuration (ip addr), check default gateway (ip route), test DNS resolution (nslookup)
Why it's wrong here
This order is incorrect because starting with ping does not isolate the problem. If ping fails, you don't know whether the issue is local IP, routing, or DNS. The logical approach is to check local configuration first.
- ✗
Check default gateway (ip route), verify IP configuration (ip addr), test DNS resolution (nslookup), ping remote host (ping)
Why it's wrong here
This order is incorrect because you should verify your own IP configuration before checking the default gateway. Without a valid IP and subnet mask, the gateway is irrelevant.
Visual reference
Go deeper
Related to this question
Learn chapter
File Transfer and Remote Access
Key term
DNS
DNS is the system that translates human-friendly domain names like example.com into machine-readable IP addresses so computers can find each other on a network.
Key term
Subnet
A subnet is a logical subdivision of an IP network, created by partitioning a larger network address space using subnet masks.
About these practice questions
This XK0-006 question is part of Courseiva's 979-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 XK0-006 practice question is part of Courseiva's free CompTIA 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 XK0-006 exam.