4.2 Given a scenario, analyze and troubleshoot network resource issues.
Objective 4.2 sits in Troubleshooting, which carries 28% of the Linux+ exam. The questions below are original, written from the official objective title above, and each explanation cites the CompTIA page it rests on.
Objective title verbatim from the official objectives. CompTIA exam page ↗
A worked example
Shown solved, with the whole explanation open: this is what every question here carries.
An administrator finds a new service will not bind to port 8080 because something already holds it. Which command shows the listening process on that port?
Correct.
Concept
Diagnosing a port conflict means listing listening sockets together with the process that owns each one.
Why B
ss -tlnp shows listening TCP sockets numerically with the owning process, revealing what already holds the port.
Now you: objective 4.2 questions
No account needed. The explanation opens when you answer.
Sample question 1 of 3
An administrator runs:
$ ss -tlnp
State Local Address:Port Process
LISTEN 0.0.0.0:22 users:(("sshd",pid=812))
LISTEN 127.0.0.1:5432 users:(("postgres",pid=990))Which service accepts connections from other hosts?
Sample question 2 of 3
An administrator finds ping 8.8.8.8 succeeds but ping example.com fails with 'Name or service not known'. What is the likely cause?
Sample question 3 of 3
After the DNS server IP changed, name lookups fail on a host. Which file's nameserver line does the administrator correct?
Full Linux+ question bank coming
We’re writing the complete bank from the official objectives right now. Leave your email and we’ll tell you when it ships, nothing else, ever.
Read the sources
These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.
More objectives in Troubleshooting
- 4.1 4.1 Given a scenario, analyze and troubleshoot storage issues.
- 4.3 4.3 Given a scenario, analyze and troubleshoot central processing unit (CPU) and memory issues.
- 4.4 4.4 Given a scenario, analyze and troubleshoot user access and file permissions.
- 4.5 4.5 Given a scenario, use systemd to diagnose and resolve common problems with a Linux system.