1.1 CompTIA Linux+ (XK0-006) Exam Structure, Passing Criteria & PBQs
Key Takeaways
CompTIA launched Linux+ V8 (XK0-006) on July 15, 2025. The prior English exam retired January 13, 2026, and its Japanese, Portuguese, and Spanish versions retired April 14, 2026.
XK0-006 has up to 90 questions in 90 minutes and a passing score of 720 on a scaled range of 100 to 900.
The five domain weights are System Management 23%, Services and User Management 20%, Security 18%, Automation, Orchestration, and Scripting 17%, and Troubleshooting 22%.
CompTIA lists simulation performance-based questions for Linux+. When you leave a simulation, your work is saved and you can return to it.
CompTIA Linux+ is valid for three years. Earning 50 Continuing Education Units under CompTIA’s rules is one renewal route.
1.1 CompTIA Linux+ (XK0-006) Exam Structure, Passing Criteria & PBQs
The current Linux+ exam
CompTIA Linux+ measures the skills needed to configure, operate, secure, and troubleshoot Linux servers. XK0-006 launched July 15, 2025. CompTIA estimates its retirement in 2028. English XK0-005 testing ended January 13, 2026, and Japanese, Portuguese, and Spanish XK0-005 testing ended April 14, 2026.
Across distributions, you will use storage and permission concepts in much the same way, while package management and other implementation choices vary. Practice the common operation and learn how to translate it. For example, a package dependency serves the same purpose on a Debian or Red Hat system even though their package managers use different syntax.
Version 8 gives dedicated objectives to Python and Git and asks candidates to recognize responsible uses of AI in administration. It also covers hands-on container operations, service management, and diagnostics.
Examination Specifications and Scoring Mechanics
The test lasts 90 minutes with a maximum of 90 items. At the maximum length, the average budget is one minute per item. If you allocate 25 minutes to longer tasks and review, you have 65 minutes for the remaining items. For example, a practice set with 75 short items gives you about 52 seconds per short item under that budget. Adjust your pace to the work in front of you.
| Specification | CompTIA Linux+ V8 |
|---|---|
| Exam code | XK0-006 |
| Launch date | July 15, 2025 |
| Number of questions | Up to 90 |
| Testing time | 90 minutes |
| Passing score | 720 on a scaled range of 100 to 900 |
| Question formats | Multiple-choice and performance-based |
| Delivery | Pearson VUE test center or eligible OnVUE online appointment |
| Recommended experience | 12 months working hands-on with Linux servers, plus A+, Network+, Server+, or similar knowledge or certifications |
| Certification validity | Three years |
A score of 720 is a scaled score. The sponsor's published cutoff gives no raw percentage or count of correct answers to target. Use practice results to find topics that need more work. Read the exact question, identify the operation it requests, and apply the relevant constraints before selecting an answer.
Domain Weighting & Objective Blueprint
The XK0-006 curriculum is partitioned into five distinct, highly practical domains. The blueprint weights highlight CompTIA's emphasis on operational reliability: System Management and Troubleshooting together constitute 45% of the published blueprint.
Domain 1.0: System Management [23%] ████████████
Domain 2.0: Services and User Management [20%] ██████████
Domain 3.0: Security [18%] █████████
Domain 4.0: Automation, Orchestration & Script [17%] ████████½
Domain 5.0: Troubleshooting [22%] ███████████
Breakdown of Objective Domains
- Domain 1.0: System Management (23%) Focuses on core Linux architecture, the boot sequence (UEFI, GRUB2, systemd targets), filesystem hierarchy (FHS), kernel modules, storage management (MBR/GPT, ext4, XFS, LVM), and network configuration tools (nmcli, Netplan, iproute2).
- Domain 2.0: Services and User Management (20%)
Encompasses user account lifecycle (
useradd,usermod,chage), process management (ps,top,kill,nice), software package management across families (DNF, APT, Zypper), systemd service/timer management, and OCI container operations (Podman). - Domain 3.0: Security (18%)
Covers PAM authentication, compliance and auditing, access control lists (POSIX ACLs), privilege escalation safeguards (
sudoers, Polkit), firewall configuration (firewalld,ufw), mandatory access control (SELinux contexts/booleans, AppArmor profiles), cryptographic keys, SSH hardening, and public key infrastructure (PKI). - Domain 4.0: Automation, Orchestration, and Scripting (17%)
Tests programmatic infrastructure management, including Bash shell scripts (loops, test conditions, parameter expansion), Python sysadmin scripts (standard library modules
os,sys,subprocess), Ansible playbooks, cloud-init provisioning, Git version control operations, and AI-assisted workflows for code generation and troubleshooting. - Domain 5.0: Troubleshooting (22%) Demands diagnostic mastery across all layers: analyzing kernel panics, resolving boot loader failures, repairing corrupt filesystems, identifying disk saturation or inode exhaustion, triaging network connectivity failures, resolving permission denials, and debugging resource bottlenecks such as high CPU load, memory leaks and I/O wait.
| Domain | Weight | Core Focus Areas | Enterprise Importance |
|---|---|---|---|
| 1.0 System Management | 23% | Boot stages, GRUB2, kernel parameters, FHS, LVM, ext4/XFS, nmcli, Netplan | Foundational platform configuration and hardware abstraction |
| 2.0 Services & User Management | 20% | User lifecycle, files and directories, process priorities, DNF/APT/Zypper, systemd units, Podman containers | Day-to-day identity governance and runtime workload operations |
| 3.0 Security | 18% | Linux firewalls, SELinux/AppArmor, sudoers, LUKS encryption, SSH keys, file permissions and audit procedures | Compliance, perimeter defense, and zero-trust node hardening |
| 4.0 Automation, Orchestration & Scripting | 17% | Bash automation, Python sysadmin scripts, Ansible, cloud-init, Git version control | Infrastructure as Code (IaC) and scalable configuration management |
| 5.0 Troubleshooting | 22% | Boot recovery, storage/inode exhaustion, network reachability, log triage (journalctl) | Incident remediation, SLA maintenance, and disaster recovery |
Practice for the two question types
For a multiple-choice item, use the scenario details. If a question asks about the current state of a running service after a repair, the unit’s active state is the relevant evidence. If it asks whether the service will start during a later boot, inspect how the system enables the unit. Read each prompt for the number of choices it requests.
CompTIA lists Linux+ under simulation performance-based questions (PBQs). A simulation can present an environment such as a terminal, network diagram, firewall, or operating system. Its controls and available commands depend on the individual task. CompTIA says you can return to a simulation later and that the interface saves work when you move to another item. The reset control can restart a simulation when you need a fresh attempt. Its use discards work on that simulation.
A two-pass approach
- Read the requirements. Underline mentally which component, state and platform the question specifies.
- If you recognize the operation and can complete it promptly, make the change and verify the requested result.
- If you spend too long figuring out a simulation, move on and return while you still have time. Track unfinished work and reserve a final pass for any item you need to review.
Worked simulation-style example
The task says to start a service now, enable it on boot, and verify both states. On a systemd host with an ordinary installable unit, systemctl enable --now example.service enables and starts the service. Check systemctl is-enabled example.service and systemctl is-active example.service separately. An enabled unit can be inactive after a failed start, and a service started manually can be active while disabled. If startup fails, inspect systemctl status example.service or the unit’s journal. Testing the requested state costs less time and causes less disruption than rebooting the host.
For a network profile task, a successful command alone leaves a second question: the profile may exist even though the interface uses a different profile now. Check the saved profile using nmcli connection show, and check the applied address using ip address show when the task asks you to activate it.
Schedule and maintain the credential
Plan delivery with Pearson VUE. At a test center, follow the facility’s admission and identification requirements. For an eligible online OnVUE appointment, run the system test on your exam device and network, follow the room and desk rules, and prepare a supported government-issued photo ID. Review the official policy before your appointment.
After a first failed attempt, you can sit attempt two without a mandatory wait. Before attempt three and later attempts, wait at least 14 calendar days after your previous attempt. Once you earn the certification, you need CompTIA’s consent to take the same passed exam code again. CompTIA listed the standalone U.S. voucher at $399 on November 17, 2026.
Linux+ is valid for three years. CompTIA’s continuing education option requires 50 Continuing Education Units (CEUs) and qualifying activities under its renewal program. Review the sponsor’s renewal options and conditions when planning to maintain the credential.
A systems administrator is reviewing the testing specifications for the CompTIA Linux+ (XK0-006) certification exam. What is the minimum passing score required, and what is the standard scoring range used by CompTIA?
680 on a scale of 100 to 1,000
720 on a scale of 100 to 900
750 on a scale of 200 to 800
800 on a scale of 100 to 900
Which of the five domains has the highest published weight in the XK0-006 blueprint?
Troubleshooting (22%)
Services and User Management (20%)
System Management (23%)
Automation, Orchestration, and Scripting (17%)
In a Linux simulation, you start and enable an installable systemd service. Which check verifies both requested states before you move on?
Run systemctl is-active example.service and systemctl is-enabled example.service
Run systemctl is-active example.service twice
Run systemctl daemon-reload alone
Reset the simulation and run systemctl is-active example.service
Sections you finish are checked off in the contents.