CompTIA · XK0-006
CompTIA Linux+ (XK0-006) Practice Tests
CompTIA Linux+ validates the skills of IT professionals to configure, manage, and troubleshoot Linux systems used in cloud, cybersecurity, and enterprise environments. It covers system administration, scripting, automation, security hardening, and container management.
Exam Details
Practice Questions
699
≈ 7 practice exams
Duration
90 minutes
Passing Score
720/900
Difficulty
AssociateLast Updated
Mar 2026
Topics Covered
System Configuration and ManagementStorage and Device ManagementNetwork ConfigurationShell Scripting and AutomationSecurity and OS HardeningUser and Account ManagementContainers and VirtualizationSoftware and Package Management
CompTIA Linux+ (XK0-006) Practice Exam Preparation
Use this XK0-006 practice exam to prepare for CompTIA Linux+ (XK0-006) with realistic questions, detailed explanations, and focused study modes. The practice bank includes 699 questions for CompTIA XK0-006, so you can review the exam steadily instead of relying on one long cram session.
As you practice, pay extra attention to recurring topics such as System Configuration and Management, Storage and Device Management, Network Configuration, Shell Scripting and Automation, and Security and OS Hardening. Start with short sessions to identify weak areas, then move into timed quizzes once your accuracy is consistent.
The explanations are especially useful when you want to connect exam wording to the responsibilities and scenarios described in the official certification guidance. Use the free preview first, then unlock the full question bank when you are ready to build a complete study routine.
Exam Domain Breakdown
System Management23%
Services and User Management20%
Security18%
Automation, Orchestration, and Scripting17%
Troubleshooting22%
Exam Overview
CompTIA Linux+ (XK0-006) validates the advanced skills of IT professionals to configure, manage, operate, and troubleshoot Linux systems in enterprise, cloud, and cybersecurity environments. This Associate-level certification demonstrates competency across system administration, storage and network configuration, security hardening, shell scripting, containerization, and troubleshooting. The exam emphasizes practical, hands-on knowledge required for modern Linux environments including hybrid cloud deployments, containerized applications, and enterprise security implementations. Successfully obtaining this certification indicates proficiency in automating tasks, implementing security best practices, and managing complex Linux infrastructure at scale.
Who Should Take This Exam
CompTIA Linux+ is designed for IT professionals with foundational Linux experience seeking to advance into system administration, cloud infrastructure, or DevOps roles. Ideal candidates include junior Linux system administrators, junior cloud engineers, junior DevOps engineers, systems engineers, and network engineers managing Linux-based infrastructure. This certification appeals to those with 12 months of hands-on Linux server experience or equivalent knowledge from CompTIA A+, Network+, or Server+ certification. Career paths include Linux systems administrator, cloud infrastructure engineer, cybersecurity operations roles, and site reliability engineer positions.
Prerequisites
Recommended prerequisites include 12 months of hands-on experience managing Linux servers in production or lab environments. While not mandatory, CompTIA strongly recommends foundational IT knowledge equivalent to CompTIA A+, Network+, or Server+ certifications. Candidates should be comfortable with command-line interfaces, basic system administration tasks, file permissions, networking concepts, and troubleshooting methodologies. Linux experience can be gained through home labs, free Linux distributions (Ubuntu, CentOS, Red Hat), or entry-level support roles. A solid understanding of basic networking, storage concepts, and security principles is beneficial.
Exam Format
The CompTIA Linux+ (XK0-006) exam consists of a maximum of 90 scored questions combining multiple-choice and performance-based (hands-on) questions. The exam is delivered online or at testing centers and must be completed within 90 minutes. The scoring scale ranges from 100 to 900, with a passing score of 720 required. Performance-based questions require candidates to demonstrate practical Linux skills in simulated environments. The exam launched July 15, 2025, and is ISO/IEC accredited by ANSI.
Skills Measured
- 1.System Management (23%): Boot processes, kernel modules, device management, storage configuration, package management, virtualization basics, and performance tuning essential for maintaining stable Linux environments
- 2.Services and User Management (20%): User and group account creation and permissions, file access controls, systemd service management, software installation and updates, container fundamentals, and time synchronization
- 3.Security (18%): Authentication mechanisms, SSH configuration, firewall management with iptables/firewalld, OS hardening, password policies, SELinux/AppArmor, cryptography basics, and compliance requirements
- 4.Automation, Orchestration, and Scripting (17%): Shell scripting with bash, basic Python scripting, task scheduling with cron and systemd timers, version control with git, configuration management principles, and responsible automation practices
- 5.Troubleshooting (22%): System monitoring and log analysis, hardware diagnostics, network connectivity troubleshooting, service failure resolution, security incident response, and performance optimization techniques
Study Tips
- Build a hands-on lab environment using free Linux distributions (Ubuntu, CentOS, or Rocky Linux) on virtual machines to practice every command and configuration covered in the five exam domains before test day
- Focus heavily on performance-based questions by practicing simulated Linux administration tasks; the exam includes hands-on questions where you must complete real system administration scenarios in a Linux environment
- Study the five core domains proportionally according to their exam weights: dedicate 23% of study time to System Management, 22% to Troubleshooting, 20% to Services and User Management, 18% to Security, and 17% to Automation
- Use CompTIA's official exam objectives document (available on their website) as your primary study guide; align your preparation materials with these published objectives to ensure comprehensive coverage
- Practice command-line proficiency daily: master essential Linux commands for file management, user administration, process management, networking, and security; performance-based questions heavily emphasize practical CLI skills
Career Benefits
CompTIA Linux+ opens doors to well-compensated roles in high-demand areas of IT. Professionals with this certification earn between $68,000 and $120,000+ annually, with average salaries around $89,000–$91,000 in the United States; experienced professionals in senior roles can exceed six figures. The certification is particularly valuable given the industry shift toward cloud computing and containerization, where Linux expertise is essential. Linux+ validates competency across critical infrastructure technologies, making certified professionals significantly more marketable than non-certified peers. Career advancement opportunities include progression to senior systems administrator, infrastructure architect, cloud engineer, or DevOps engineer roles, with steady salary growth potential as experience accumulates.
Sample Questions
5 sample questions with answers and explanations. The full bank has 699 questions, enough for 7 full-length practice exams.
Preview — answers shown1. A systems administrator at Contoso Ltd. is hardening an SSH server according to CIS Benchmark recommendations. The security policy requires that root must never be able to authenticate to the server via SSH using any method — including SSH key authentication — while still permitting root to log in at the local console. Which sshd_config directive and value should the administrator set? (Select one!)
APermitRootLogin forced-commands-only
BPermitRootLogin no
CDenyUsers root
DPermitRootLogin prohibit-password
Explanation
PermitRootLogin no completely blocks all SSH-based root login attempts, including both password authentication and public key authentication. This directive has no effect on local console logins, which are governed by PAM and the /etc/securetty file, so the requirement to allow local root access is fully preserved. PermitRootLogin prohibit-password blocks password-based root logins but still permits root to authenticate via SSH public key, which does not satisfy the requirement to block all SSH root access. PermitRootLogin forced-commands-only allows root to authenticate via SSH public key when a forced command is specified in the authorized_keys file — again allowing key-based SSH access. DenyUsers root is a valid alternative mechanism that prevents the root account from authenticating via SSH; however, PermitRootLogin no is the canonical, purpose-built directive for this specific goal and is the standard hardening setting documented by CIS and most Linux security guides.
2. A systems administrator at Northwind Traders is examining a server that has recently been rebooted. The administrator needs to view log messages from the previous boot session to investigate why the system rebooted unexpectedly. Which command should the administrator use? (Select one!)
Ajournalctl -b -1
Bjournalctl -b 0
Cjournalctl --since yesterday
Ddmesg -T | grep -i reboot
Explanation
journalctl -b -1 displays log entries from the previous boot session. The -b flag specifies a boot ID offset, where -1 refers to the last boot before the current one, -2 refers to two boots ago, and so on. This is the correct way to investigate issues that occurred in a prior boot session. journalctl --since yesterday would show logs from the past 24 hours but includes the current boot and may miss events if the reboot happened more than a day ago. journalctl -b 0 or simply journalctl -b shows logs from the current boot session, not the previous one. dmesg -T only shows kernel ring buffer messages from the current boot and cannot access previous boot logs. Note that viewing previous boot logs requires persistent journal storage to be configured with Storage=persistent in /etc/systemd/journald.conf.
3. A systems administrator at Contoso needs to configure a Linux server to permanently route traffic between two network segments. The server must continue forwarding packets after every reboot without any manual intervention. Which approach correctly achieves persistent IP forwarding? (Select one!)
ASet net.ipv4.ip_forward=1 using the ip command and configure NetworkManager to preserve it
BWrite '1' directly to /proc/sys/net/ipv4/ip_forward using a startup script
CAdd net.ipv4.ip_forward=1 to /etc/sysctl.conf and run sysctl -p to apply it
DRun 'sysctl -w net.ipv4.ip_forward=1' and add the command to /etc/rc.local
Explanation
Adding net.ipv4.ip_forward=1 to /etc/sysctl.conf and then running sysctl -p is the correct and standard method for making kernel parameter changes persist across reboots. The sysctl -p command reads the configuration file and applies all settings immediately without requiring a reboot. Changes made with sysctl -w are runtime-only and are lost when the system restarts, even if placed in rc.local, because rc.local execution is not guaranteed on all systemd-based distributions. Writing directly to /proc/sys/net/ipv4/ip_forward is also a runtime-only change; the /proc filesystem is a virtual interface to the running kernel and its values reset on reboot. The ip command does not manage kernel sysctl parameters, and NetworkManager does not control kernel forwarding settings.
4. A systems administrator at Adatum Corporation needs to create a new ext4 filesystem on /dev/sdb1 and ensure it is automatically mounted at /data at boot with the following requirements: read-write access, UUID-based identification to survive disk reordering, filesystem check skipped for this data volume, and the system should still boot if the disk is unavailable. Which /etc/fstab entry meets all requirements? (Select one!)
AUUID=abc123 /data ext4 defaults 0 0
B/dev/sdb1 /data ext4 defaults,nofail 0 2
CUUID=abc123 /data ext4 defaults,nofail 0 0
DUUID=abc123 /data ext4 defaults 1 2
Explanation
UUID=abc123 /data ext4 defaults,nofail 0 0 satisfies all stated requirements. Using the UUID instead of the device path ensures the correct partition is mounted even if disk ordering changes when additional disks are added. The nofail mount option instructs the system to continue booting even if this filesystem cannot be mounted, preventing a boot failure if the disk is unavailable. The fifth field (dump) set to 0 disables dump backups. The sixth field (fsck order) set to 0 explicitly skips filesystem checks for this volume at boot. Using /dev/sdb1 instead of UUID violates the UUID requirement and is unreliable. The entry with fsck order 2 would run filesystem checks on this volume, contradicting the skip requirement. The entry without nofail would cause boot failures if the disk is removed or unavailable.
5. A systems administrator at Northwind Traders is troubleshooting a server where a user reports that after their SSH session disconnects, a long-running data processing script stops running. The script is started without any job control. Which two methods would allow the script to continue running after the SSH session terminates? (Select two!)
Multiple correct answersARun the script with 'nohup ./script.sh &' to detach it from the terminal
BRun the script with 'nice -n 19 ./script.sh' to lower its priority
CUse 'screen' or 'tmux' to run the script inside a multiplexer session
DAdd 'set -e' at the top of the script to prevent it from terminating on errors
ERun the script as 'sudo ./script.sh &' so it runs with elevated privileges
Explanation
When an SSH session terminates, the kernel sends SIGHUP to the session leader, which propagates to all child processes, causing them to terminate. Two methods prevent this. nohup (no hangup) runs a command immune to SIGHUP signals; the & background operator detaches it from the terminal's foreground. Using nohup ./script.sh & causes the script to ignore SIGHUP and continue running even after the terminal closes, with output redirected to nohup.out. Screen and tmux are terminal multiplexers that create persistent sessions on the server; the SSH user connects to the multiplexer session rather than directly to the shell, so disconnecting SSH does not affect processes inside the multiplexer. nice -n 19 only adjusts CPU scheduling priority and has no effect on process lifetime or SIGHUP handling. set -e is a bash error-handling option unrelated to session termination. Running with sudo changes privilege level but does not prevent SIGHUP.
More CompTIA Practice Exams
$17.99
One-time access to this exam
699 questions (7 practice exams' worth)
Unlimited timed exam simulations
Yours forever — no subscription
Detailed explanations
Free preview stays available