Bird
0
0

You want to diagnose why your server cannot reach a remote host. Which sequence of commands is best to identify the problem?

hard📝 Application Q8 of 15
Linux CLI - Networking Commands
You want to diagnose why your server cannot reach a remote host. Which sequence of commands is best to identify the problem?
AOnly use traceroute because ping is unreliable
BRestart the server before running any commands
CFirst use ping to check reachability, then traceroute to find where packets stop
DUse ping with a very high packet count to flood the network
Step-by-Step Solution
Solution:

  1. Step 1: Understand diagnostic steps

    Ping quickly checks if the host is reachable; if not, traceroute helps find where packets fail.

  2. Step 2: Evaluate other options

    Only traceroute misses quick reachability check; restarting or flooding network is not diagnostic.

  3. Final Answer:

    First use ping to check reachability, then traceroute to find where packets stop -> Option C

  4. Quick Check:

    Ping then traceroute = Best diagnostic sequence [OK]
Quick Trick: Ping first, traceroute next to diagnose connectivity [OK]
Common Mistakes:
  • Skipping ping
  • Restarting unnecessarily
  • Flooding network with pings

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Linux CLI Quizzes
Networking Commands - scp and rsync for file transfer - Quiz 12easy Networking Commands - ping for connectivity testing - Quiz 13medium Pipes and Redirection - Why pipes chain commands into workflows - Quiz 12easy Pipes and Redirection - tee for splitting output - Quiz 11easy Pipes and Redirection - tee for splitting output - Quiz 14medium Pipes and Redirection - stderr redirection (2>, 2>>) - Quiz 7medium Process Management - ps (list processes) - Quiz 3easy Process Management - systemctl for service management - Quiz 15hard Searching and Finding - Why finding files saves time - Quiz 2easy Text Processing - tr (translate characters) - Quiz 6medium