easyMultiple Choice
XK0-006 Troubleshoot a system that is not booting Practice Question
A technician needs to troubleshoot a system that is not booting. Which of the following is the most appropriate first step when using a rescue environment?
⚠ Common exam trap
The trap here is that candidates often jump to checking logs or running fsck first, not realizing that without mounting the root filesystem, those actions are either impossible or operate on the rescue environment's own filesystem rather than the broken system's data.
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
✓
Mount the root filesystem to /mnt/sysimage.
When using a rescue environment, the first priority is to gain access to the system's configuration and log files by mounting the root filesystem. Mounting to /mnt/sysimage (a conventional mount point in Red Hat-based rescue modes) allows the technician to chroot into the environment and treat it as the running system, enabling further troubleshooting steps like checking logs or repairing the bootloader. This step is foundational because without the root filesystem mounted, commands like checking logs or running fsck cannot operate on the actual system data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Mount the root filesystem to /mnt/sysimage.
Why this is correct
Mounting the root filesystem to /mnt/sysimage exposes the installed system's files, configuration and logs to the rescue environment, enabling chroot-based repair. This is the standard first step before diagnosing boot failures such as damaged bootloaders or misconfigured fstab entries.
- ✗
Check the system logs in /var/log/messages.
Why it's wrong here
Logs in /var/log/messages are written by the running system, so they are unavailable when boot fails before the logging service starts; the rescue environment's own logs and dmesg are needed instead. It is tempting because log review is a sound diagnostic habit, and would be correct on a system that boots but misbehaves.
- ✗
Run fsck on all partitions.
Why it's wrong here
Running fsck across all partitions modifies filesystem metadata before the underlying fault is identified, risking further damage on a system that may simply have a configuration error. It is tempting because filesystem corruption commonly prevents booting, and would be correct once logs or mount failures point to it.
- ✗
Reinstall the bootloader immediately.
Why it's wrong here
Reinstalling the bootloader overwrites configuration before the cause of the failure is known, potentially destroying evidence or worsening the fault. It is tempting because bootloader corruption is a common cause, and would be correct once diagnosis confirms the bootloader is actually damaged.
Go deeper
Related to this question
Learn chapter
System Troubleshooting and Performance Tuning
Key term
fsck
fsck is a command-line tool that checks and repairs inconsistencies in a file system, ensuring data integrity.
Key term
Mount
Mounting is the process of making a file system or storage device accessible to a computer's operating system by attaching it to a specific directory in the existing directory tree.
About these practice questions
One of 781 original XK0-006 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.