CompTIA Linux+ XK0-006 Course and Lab Path
Table of Contents
CompTIA Linux+ v8 uses exam XK0-006. This course follows its five domains. The former XK0-005 exam used four domains with different weights. Check the official XK0-006 objectives before you study. Use the objectives as a checklist because this course includes selected examples, not every command or scenario in the blueprint.
You need a disposable Linux virtual machine, a non-root account with authorized sudo access, a snapshot, and a terminal. The examples use Debian or Ubuntu where noted. Package names and service units differ by distribution. Never practice partitioning, firewall changes, or account lockout on a production host. Record commands, output, changes, and rollback in a private lab log.
| XK0-006 domain | Weight | Lesson | Evidence to produce |
|---|---|---|---|
| 1. System Management | 23% | System Management | Storage and network inventory, backup and restore result |
| 2. Services and User Management | 20% | Services and User Management | Least privilege account, service state, logs, and container result |
| 3. Security | 18% | Linux Security | Permission and firewall checks with denied and allowed tests |
| 4. Automation, Orchestration, and Scripting | 17% | Automation and Scripting | Repeatable script, test output, and rollback |
| 5. Troubleshooting | 22% | Linux Troubleshooting | Symptom, hypothesis, evidence, repair, and verification |
Exact beginner lab setup
Use Canonical Multipass on Windows, macOS, or Linux. Install it from Canonical’s linked release or package route and open your normal terminal: PowerShell on Windows, Terminal on macOS, or a shell on Linux. If installation requires administrator approval on a managed computer, use an approved device or ask its owner. The VM uses a virtual network which may reach other systems. Keep only fictional data in it and do not scan outside the VM.
Run these commands on the host terminal, one at a time:
multipass version
multipass find
multipass launch 24.04 --name linuxplus-lab --cpus 2 --memory 4G --disk 20G
multipass info linuxplus-lab
multipass shell linuxplus-lab
The find output should list 24.04 as an Ubuntu LTS image. info should show a running instance, release, CPU and memory allocation, and an image hash reported by Multipass. The displayed image hash identifies the fetched image in the manager. It is not a manually verified ISO checksum. Do not claim a manual SHA-256 comparison unless you download and verify a separate image yourself. If the launch fails, use multipass info linuxplus-lab to see whether an instance was created before retrying. Do not launch another instance with the same name.
Inside the VM, the prompt changes. Run:
cat /etc/os-release
id
sudo -v
sudo -l
mkdir -m 700 -p "$HOME/linuxplus-lab/evidence"
ip -brief address
Expect Ubuntu 24.04 in /etc/os-release, a non-root user from id, and an authorized sudo route in sudo -l. The exact network interface and address vary, so record the observed values rather than using eth0 by assumption. Keep evidence under the private folder. Do not paste passwords into the log. If sudo -v fails, stop the privileged exercises and use the read-only study route.
Type exit to return to the host. If your Multipass driver supports snapshots, stop the VM and create a named baseline:
multipass stop linuxplus-lab
multipass snapshot linuxplus-lab --name linuxplus-base
multipass start linuxplus-lab
Snapshots are not available on every backend, including AppleVZ. Check multipass help snapshot and the result rather than assuming success. The portable reset is to save only your text evidence outside the VM, then delete the named disposable instance and relaunch the same 24.04 image. multipass delete --purge linuxplus-lab permanently removes that VM and its files. Run it only when you have saved the work you need.
Multipass snapshot and restore guidance
explains supported behavior.
Self-check rubric
For each of the five domain lessons, score one point for the baseline, one for an exact task and expected result, one for observed output, one for a controlled fault and diagnosis, and one for cleanup or rollback. A lesson passes at 5 of 5. A not run result records a gap, not a pass. If you have no reviewer, hide the worked example, perform the task, then compare your evidence with its expected result. Redo the task after a reset if any item is missing. The full XK0-006 objectives include more subjects than these five checkpoints, so use the official PDF for additional study.
Work Through One Lab System
Start from a clean snapshot named linuxplus-base. Create a private evidence directory outside shared or public web roots. Record the distribution and release with cat /etc/os-release, the kernel with uname -r, your identity with id, and the network with ip -brief address. Treat these observations as your baseline.
- System Management: identify mounts and free space with
lsblk -fanddf -h. Create a small file tree in your home directory, archive it withtar, restore it to a separate path, and compare the files. Do not run disk-format commands on the boot device. - Services and users: create a disposable lab account through an approved administrator route. Give it only the rights needed for a named task. Start, inspect, and stop a lab service. Capture
systemctl statusandjournalctl -uoutput. Remove the account and service override after recording evidence. - Security: set file ownership and permissions on a disposable directory. Test allowed and denied access from two lab identities. Check host firewall status before a rule change. Maintain console access and a rollback route.
- Automation: write a shell script that checks a named service and records a timestamp. Run it twice against the same state, capture output and exit codes, and verify it does not duplicate or overwrite unrelated data.
- Troubleshooting: inject a safe fault on a disposable service, such as an invalid path in a lab unit. Record the symptom, gather status and logs, repair the path, and demonstrate a successful restart. Restore the baseline snapshot when done.
Check Your Work
A reviewer should be able to follow your lab log without guessing the host, command order, or expected result. For each domain, include the initial state, task, command or UI path, observed output, one failure and its cause, verification, and rollback. Redact credentials and personal data. A successful command with no read-back does not show the final state.
Use the Linux+ practice test to find recall gaps. Then check each numbered official objective against a lab result or a deliberate study note. The practice test and five lessons are study aids. They do not replace the official blueprint or hands-on assessment.
