- A
The installation script did not install all required dependencies.
The 'not found' libraries indicate missing dependencies, which can occur if the script failed to install all required packages.
- B
The kernel version is outdated.
Why wrong: Kernel version would affect system calls, not library visibility.
- C
SELinux is blocking the application.
Why wrong: SELinux denials appear in audit logs, not as missing libraries from ldd.
- D
The file system is corrupted.
Why wrong: File system corruption would typically cause I/O errors, not missing library messages.
Quick Answer
The answer is that the installation script did not install all required dependencies. This is the most likely cause because the `ldd` command, when used to check a binary like `/usr/bin/app`, reveals missing shared library dependencies by listing them as "not found," which means the dynamic linker cannot locate the necessary `.so` files. On the CompTIA Linux+ XK0-005 exam, this scenario tests your understanding of how package management and dependency resolution work—specifically, that a custom shell script may bypass a package manager's automatic dependency handling, leaving the binary broken. A common trap is assuming the repository itself is faulty, but the key clue is that `ldd` shows specific missing libraries, pointing directly to incomplete installation. Remember the mnemonic: "LDD: List Dependencies, Diagnose Deficits"—if you see "not found," the install step likely missed those files.
XK0-005 Troubleshooting Practice Question
This XK0-005 practice question tests your understanding of troubleshooting. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A user reports that a recently installed application fails to start. The application was installed via a shell script that added a repository and installed the package. The user runs 'ldd /usr/bin/app' and sees several 'not found' libraries. Which of the following is the MOST likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
The installation script did not install all required dependencies.
The `ldd` command lists shared library dependencies for a binary. When it reports 'not found' libraries, it means the dynamic linker cannot locate the required `.so` files. Since the application was installed via a shell script that added a repository and installed the package, the most likely cause is that the script failed to install all required dependencies, leaving the binary unable to resolve its shared library links.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The installation script did not install all required dependencies.
Why this is correct
The 'not found' libraries indicate missing dependencies, which can occur if the script failed to install all required packages.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The kernel version is outdated.
Why it's wrong here
Kernel version would affect system calls, not library visibility.
- ✗
SELinux is blocking the application.
Why it's wrong here
SELinux denials appear in audit logs, not as missing libraries from ldd.
- ✗
The file system is corrupted.
Why it's wrong here
File system corruption would typically cause I/O errors, not missing library messages.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse library resolution failures with permission or security issues (like SELinux), but `ldd` output directly points to missing files, not access control.
Detailed technical explanation
How to think about this question
The dynamic linker (`ld-linux.so`) resolves shared library dependencies at runtime by searching paths in `/etc/ld.so.conf` and the `LD_LIBRARY_PATH` environment variable. The `ldd` command uses the dynamic linker to simulate this resolution, so 'not found' indicates the library is not present in any standard search path. In real-world scenarios, package managers like `apt` or `yum` handle dependency resolution automatically, but a custom shell script that adds a repository and installs a package may skip `--install-recommends` or fail to run `apt-get install -f`, leaving unmet dependencies.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the XK0-005 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Troubleshooting — study guide chapter
Learn the concepts, then practise the questions
- →
Troubleshooting practice questions
Targeted practice on this topic area only
- →
All XK0-005 questions
510 questions across all exam domains
- →
CompTIA Linux+ XK0-005 study guide
Full concept coverage aligned to exam objectives
- →
XK0-005 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related XK0-005 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Security practice questions
Practise XK0-005 questions linked to Security.
Troubleshooting practice questions
Practise XK0-005 questions linked to Troubleshooting.
Scripting, Containers and Automation practice questions
Practise XK0-005 questions linked to Scripting, Containers and Automation.
System Management practice questions
Practise XK0-005 questions linked to System Management.
XK0-005 fundamentals practice questions
Practise XK0-005 questions linked to XK0-005 fundamentals.
XK0-005 scenario practice questions
Practise XK0-005 questions linked to XK0-005 scenario.
XK0-005 troubleshooting practice questions
Practise XK0-005 questions linked to XK0-005 troubleshooting.
Practice this exam
Start a free XK0-005 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this XK0-005 question test?
Troubleshooting — This question tests Troubleshooting — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The installation script did not install all required dependencies. — The `ldd` command lists shared library dependencies for a binary. When it reports 'not found' libraries, it means the dynamic linker cannot locate the required `.so` files. Since the application was installed via a shell script that added a repository and installed the package, the most likely cause is that the script failed to install all required dependencies, leaving the binary unable to resolve its shared library links.
What should I do if I get this XK0-005 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
This XK0-005 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-005 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.