RoleMath Study Track for CompTIA Server+ (SK0-005)
A free study companion keyed to the officially published exam domains of CompTIA Server+ (SK0-005): what each domain covers in plain language, clearly labeled free resources, a guided lab outline for every domain, and interactive self-checks from our own question bank. CompTIA Server+ (SK0-005) exam objectives
A free, source-cited study companion built on CompTIA's published Server+ (SK0-005) exam objectives — not official training, not a pass guarantee. Server+ has a thinner free ecosystem than A+ or Network+: there is no free Professor Messer course and no free CertMaster trial for it, so the honest free path is the official objectives as your scope anchor plus a hands-on lab you build yourself from free virtualization and free server operating systems. Every lab here runs only on virtual machines you own on your own hardware; snapshot before you start and revert afterward. Verify the current objectives on the official page before your exam.
A free, honestly-scoped CompTIA Server+ (SK0-005) program pinned to the currently published exam objectives, sequenced the way a real server estate is built — hardware and storage foundation first, then the heaviest administration domain, then security and disaster recovery, and finally troubleshooting with an integrated capstone. It does not pretend a complete free video course exists: Server+ has no free Professor Messer course and no free CertMaster trial, so the free path is the official objectives as your scope anchor plus a lab you assemble yourself from free virtualization (VirtualBox) and free server operating systems (Ubuntu Server, Rocky Linux, and the time-boxed Windows Server 2022 Evaluation), every lab run only on VMs you own with a snapshot before and a revert after. This is an intermediate program that assumes A+/Network+ level fundamentals, and it recommends rechecking the official objectives before any exam scheduling.
This draft exposes RoleMath’s authored sequence and evidence plan. The current labs are guided outlines, not yet a fully fixture-backed course, and objective-leaf coverage has not passed the gold-standard gate. Completion does not predict an exam result.
Modules
4
Labs
4
Concept checks
12
Resource mix
3 official / 0 community
Choose an outcome
Three routes through the same evidence
Choose provisionally. Change routes when the work tells you something new about fit, time, or readiness.
Certification-focused
Learners with A+/Network+ level fundamentals and some hands-on server exposure who want one current, dependency-ordered SK0-005 sequence across all four domains, with every lab run only on VMs they own (snapshot before, revert after) and a recheck of the official objectives before scheduling.
Completion emphasis: Complete every module in published order, run each domain lab only on VMs you own with snapshots reverted, correct every missed check against its cited source, finish the integrated build-harden-back-up-and-troubleshoot capstone on your own lab, and diff the current objectives before booking the exam — never inferring a score from coverage.
Required phases: Server hardware, storage, and VM-lab foundation, Server administration — the heaviest domain, Security and disaster recovery — protect and be ready to recover, Troubleshooting methodology and integrated capstone
Server-admin skills first
Career changers with prior IT, help-desk, or desktop-support experience who want reviewable evidence that they can stand up core server services, harden and back up a server, and diagnose a failure methodically on hardware they own, whether or not they sit the exam soon.
Completion emphasis: Retain a labeled artifact per domain — a RAID build-fail-rebuild record, a domain-controller-plus-DNS/DHCP build note, a hardening-and-verified-restore record, and a completed seven-step troubleshooting runbook — plus the capstone evidence packet and a snapshot-revert confirmation proving every lab ran on your own disposable VMs.
Required phases: Server hardware, storage, and VM-lab foundation, Server administration — the heaviest domain, Security and disaster recovery — protect and be ready to recover, Troubleshooting methodology and integrated capstone
Career-fit sprint
Learners deciding whether server administration — racking-and-storage thinking, standing up directory and network services, and the operational discipline of hardening, backup, and methodical troubleshooting — is a direction worth deeper investment before committing to the full SK0-005 exam grind.
Completion emphasis: Complete the diagnostic, the hardware-and-lab foundation, and the heaviest server-administration phase with their labs on your own VMs, then choose a next server experiment or a full exam commitment rather than inferring job readiness or a pass from partial coverage.
Required phases: Server hardware, storage, and VM-lab foundation, Server administration — the heaviest domain
Start safely
Prerequisite diagnostic
Confirm you meet the intermediate bar and can build a VM lab before the Server+ labs; this diagnostic is not a CompTIA prerequisite, a cost promise, or an exam prediction, and CompTIA recommends roughly two years of hands-on server experience plus A+/Network+ level knowledge for SK0-005. A determined learner without all of that can still follow the free path but should expect to build the underlying fundamentals along the way.
Do you already have A+/Network+ level fundamentals — how a computer is assembled, storage and RAID basics, and TCP/IP, DNS, DHCP, subnets, and common protocols — since Server+ builds directly on that layer and does not re-teach it in depth?
Ready when: Yes, or you will review A+ and Network+ level fundamentals (or those tracks) alongside Domain 1 and Domain 2 rather than learning the baseline and the server material at once.
If not yet: Spend time on A+/Network+ level fundamentals (or those tracks) first, because Server+ is not a first-ever IT certification and assumes that hardware, OS, and networking baseline.
Can you build a VM lab on your own hardware — VirtualBox with an Ubuntu Server or Rocky Linux VM, and enough RAM and disk to also run the Windows Server 2022 Evaluation for the administration domain?
Ready when: Yes, with enough RAM and disk to run at least one Linux server VM and, for Domain 2, the Windows Server Evaluation, all on an isolated Host-Only network.
If not yet: Start with the lighter Linux-only labs on a single low-memory VM and use the documentation-based study route for the hardware and Windows Server portions until you can run heavier VMs.
Are you comfortable with command-line basics on both sides — a Linux shell (bash) with sudo for the storage, hardening, and troubleshooting labs, and PowerShell run as Administrator for the Windows Server administration lab?
Ready when: Yes, or you will follow each lab's documented command steps while building bash and PowerShell fluency in parallel.
If not yet: Practice basic Linux CLI and PowerShell (a free fundamentals resource or the Linux+ track) before the storage and administration labs, because every lab assumes you can run and read commands.
Do you understand that the Windows Server 2022 Evaluation used in the administration lab is free but requires a free Microsoft account to download and is time-boxed to 180 days from first boot, so its VM is disposable and not a long-lived server?
Ready when: Yes, and you will note the 180-day expiry, create a free Microsoft account for the download, and treat that VM as a disposable lab that you revert to snapshot.
If not yet: Use the free, no-expiry Linux server operating systems (Ubuntu Server, Rocky Linux) for the services you can practice there, and study the Windows-specific directory material from documentation until you can set up the evaluation.
Have you chosen a pace whose weekly hours you can realistically protect across roughly 60 to 130 total hours depending on your prior server and lab experience?
Ready when: Yes, with a pace selected and the objective recheck, the lab snapshot-and-revert steps, and the capstone left uncompressed.
If not yet: Pick the steady pace if you have limited server experience and reserve the intensive pace for learners who already hold A+/Network+ and have server experience; never compress the snapshot, revert, and verification steps to save time.
Plan, then adapt
Pace options
Steady
14 weeks 8-10 hours/week
A planning estimate of roughly 100-130 hours for an A+ holder with limited hands-on server experience: one domain block at a time, every lab run only on VMs you own with a snapshot taken before and reverted after, plus the integrated capstone and an objectives recheck before scheduling. Give Domain 2 (administration, 30%) the most time and Domain 4 (troubleshooting, 28%) close behind.
Standard
10 weeks 10-12 hours/week
A planning estimate for learners with some hands-on server exposure that pairs the CompTIA-cited domain study with one retained artifact per domain and preserves the integrated build-harden-back-up-and-troubleshoot capstone, the missed-check corrections, and an objectives-diff block before any exam logistics.
Intensive
7 weeks 12-14 hours/week
Roughly 60-80 hours for a learner who already holds A+/Network+ and has hands-on server experience; do not compress the VM snapshot-and-revert discipline, the verified backup-restore drill, the seven-step troubleshooting methodology, or the note that the Windows Server Evaluation is disposable and expires after 180 days.
Evidence-gated sequence
Program roadmap
1
Server hardware, storage, and VM-lab foundation
Build the physical-and-storage foundation the whole certification sits on (Domain 1, 18%): racks, redundant power and cooling, drive interfaces, RAID levels, firmware, and out-of-band management — and stand up the VirtualBox lab, on your own hardware and an isolated Host-Only network, that every later domain reuses, practicing RAID hands-on with free software RAID while reading vendor docs for the hardware-controller specifics VirtualBox cannot emulate.
Complete the software-RAID lab on an Ubuntu Server VM you own: add four virtual disks, build a RAID 1 mirror with mdadm, deliberately fail and rebuild a member with the data intact, and create a RAID 5 array — reasoning about usable capacity, fault tolerance, and rebuild behavior — then revert the VM to its pre-lab snapshot.
Note in writing what a hardware RAID controller adds (battery-backed cache, controller-level rebuilds, out-of-band health) that software RAID in a VM cannot demonstrate, using HPE iLO / Dell iDRAC documentation, so the honest gap in the free lab is explicit.
Complete the hardware/networking-fundamentals, VM-lab, command-line, Windows-evaluation-account, and study-time diagnostics, choose a pace you can protect, and be able to state why redundancy and out-of-band management are load-bearing server-hardware concepts.
Attempt every authored Server-hardware-installation-and-management check and correct each miss against its cited source before moving to server administration.
2
Server administration — the heaviest domain
Work the single heaviest domain (Domain 2, 30%) with the most study time: install a server operating system, stand up the core network services an organization depends on (DNS, DHCP, NTP, directory), and understand storage services, high availability, virtualization, scripting, asset management, and licensing — building the running systems the security and troubleshooting domains later defend and diagnose, all on VMs you own on an isolated Host-Only network.
Complete the administration lab: install the free (180-day) Windows Server 2022 Evaluation on an isolated Host-Only network, promote it to a domain controller for a fictional lab domain (labdomain.local) with integrated DNS, authorize a DHCP scope, and create an organizational unit, a user, and a security group — then revert the VM to its pre-lab snapshot rather than uninstalling.
Explain how core services depend on each other (directory services relying on DNS and NTP) and match a virtualization, storage-services, or high-availability technology to a described availability or storage goal, noting the 180-day evaluation expiry so the disposable VM is not mistaken for production.
Retain a build note for the directory-plus-services stack you stood up, verified with Get-ADDomain, Get-DhcpServerv4Scope, and Resolve-DnsName, all confined to the isolated lab domain.
Attempt every authored Server-administration check and correct each miss against its cited source, giving this heaviest domain the most study time before moving to security and disaster recovery.
3
Security and disaster recovery — protect and be ready to recover
Add the discipline that protects the running servers you just built (Domain 3, 24%): data security and encryption, identity and least-privilege access, hardening and patch management, secure decommissioning, backup strategy (full/incremental/differential, the 3-2-1 rule), recovery objectives (RTO and RPO), and disaster-recovery planning — proving both the hardening and a verified restore hands-on on a VM you own.
Complete the hardening-and-backup lab on an Ubuntu Server VM you own: enable automatic security updates, set a default-deny firewall allowing only SSH, disable direct root SSH login, create a least-privilege sudo user, audit the result with Lynis, then run a 3-2-1-aware backup, delete a file to simulate data loss, and successfully restore it — then revert the VM to its pre-lab snapshot.
Record the RTO/RPO reasoning for the restore drill and be able to explain the 3-2-1 rule, why an untested backup is not a trustworthy backup, and which hardening steps most reduce a described server's attack surface.
Retain a hardening-and-verified-restore record (firewall status, disabled root SSH, least-privilege user, Lynis score, and the deleted-then-restored file), produced only on a VM you own with sample data and no real credentials.
Attempt every authored Security-and-disaster-recovery check and correct each miss against its cited source, tracing why secure decommissioning and tested recovery are examinable and often-overlooked.
4
Troubleshooting methodology and integrated capstone
Apply CompTIA's structured seven-step methodology to the whole stack (Domain 4, 28% — the second-heaviest domain) by deliberately breaking a service on a VM you own and diagnosing it with status, config-test, and journal tools, then integrate all four domains in the capstone: build a small server, harden it, back it up, and troubleshoot an injected fault, documenting throughout, all on your own disposable VMs.
Complete the troubleshooting lab on an Ubuntu Server VM you own: deliberately break nginx with an invalid configuration line, walk the seven-step methodology (systemctl status, nginx -t, journalctl) to localize the exact bad line, restore and verify the service is active, document all seven steps in the runbook, and run the wider checks (systemctl --failed, df -h) — then revert the VM to its pre-lab snapshot.
Explain why verifying full functionality and documenting findings are examinable steps the methodology explicitly rewards, and how the same process transfers to hardware, storage, network, and security faults across the earlier domains.
Complete the integrated capstone spanning all four domains — build a small server with a role and storage, harden it, back it up, then troubleshoot an injected fault, documenting throughout — against your own isolated VMs, then revert every VM and verify nothing persists.
Diff the current CompTIA Server+ objectives, record remaining gaps, and choose a continue, practice, defer, server experiment, or exam-scheduling next decision rather than inferring a pass from coverage.
Before a lab
Environment, access, and safety
Required and optional setup
Required
A browser plus text, spreadsheet, and diagram tools for the CompTIA-cited objectives, vendor documentation, and for recording each lab's build notes, findings, evidence, and snapshot-revert confirmation
VirtualBox (free) on your own hardware with enough RAM and disk to run at least one Linux server VM (Ubuntu Server or Rocky Linux) and, for the administration domain, the Windows Server 2022 Evaluation, all on an isolated Host-Only network
The free server operating systems the labs use — Ubuntu Server and Rocky Linux (free, no expiry) and the Windows Server 2022 Evaluation (free but time-boxed to 180 days and requiring a free Microsoft account) — installed as disposable VMs you own
The free tooling the labs use inside those VMs — mdadm for software RAID, the built-in Server Manager and PowerShell on Windows Server, UFW, unattended-upgrades, OpenSSH, rsync, and Lynis on Linux, and systemctl/journalctl/nginx for the troubleshooting drill
A per-lab snapshot-and-revert ledger recording, for each lab, that a snapshot was taken before, the lab ran only on VMs you own, and every VM was reverted to its pre-lab state afterward
Optional
HPE iLO and Dell iDRAC server documentation, open in a browser, for the hardware-RAID-controller and out-of-band-management specifics VirtualBox cannot emulate
A free DigitalOcean or vendor mdadm/administration tutorial as an alternate explanation alongside the official objectives (community-produced — verify it is free and current before relying on it)
A second Linux server VM on the same isolated Host-Only network to practice service-to-service dependencies (for example a client resolving names against your lab DNS) on hardware you own
Accounts and accessibility routes
Accounts
The Linux labs require no account and no payment: Ubuntu Server, Rocky Linux, VirtualBox, and every tool the labs use are free downloads, and each lab runs on an isolated Host-Only network on hardware you own.
The Windows Server administration lab requires a free Microsoft account to download the Windows Server 2022 Evaluation, which is free but time-boxed to 180 days from first boot — note the expiry and treat that VM as disposable, not a long-lived server.
No lab requires a paid subscription, a cloud account, or a card; if you cannot or prefer not to set up the Windows evaluation, practice the equivalent services on the free Linux server operating systems and study the Windows-specific directory material from documentation.
Equivalent routes
When running heavy VMs is impractical for device, memory, motor, or account reasons, use lighter Linux-only labs on a single low-memory Ubuntu Server or Rocky Linux VM (the RAID, hardening, backup, and troubleshooting labs all run there) and study the hardware domain and the Windows Server directory material from documentation, recording a written expected-state walkthrough labeled documentation-based instead of a live build.
Every Linux lab is command-line and text driven and every Windows Server step has a PowerShell equivalent to the GUI, so the whole program is keyboard-operable with plain-text tool output a screen reader can read linearly; the build notes, hardening record, and troubleshooting runbook are plain Markdown with labeled headings and fields.
In low-bandwidth conditions the labs run inside local VMs with no ongoing internet traffic after the one-time OS and package downloads; if a hardware step cannot be executed at all, study the objective, read the vendor documentation, and record a written expected-state walkthrough labeled documentation-based.
Safety baseline
Run every lab ONLY on virtual machines you own on your own hardware — never on a physical server, a production or shared machine, a machine anyone depends on, or any system you do not own.
Keep every lab VM on an isolated Host-Only network (never a Bridged adapter that could reach your real network or the internet), especially the domain controller, so the lab domain (labdomain.local) can never touch a real production domain or network.
Snapshot every VM before you start and revert it to that pre-lab snapshot afterward so nothing persists; treat the destructive disk commands (mdadm), the firewall/SSH hardening changes, and the deliberate service break as safe only inside a disposable snapshotted VM.
Use only fictional lab identities, throwaway passwords confined to the lab VM, and sample data; never place real credentials, personal data, or secrets on a lab server, and never reuse a real password for a lab account.
Note that the Windows Server 2022 Evaluation is free but expires 180 days after first boot and that VirtualBox cannot emulate a hardware RAID controller — treat the evaluation VM as disposable and supplement the hardware-controller specifics with HPE/Dell documentation rather than mistaking software RAID for hands-on with an enterprise controller.
Show your work
Module evidence and missed-check protocol
Module exit evidence
A labeled artifact per domain tied to its module: a RAID build-fail-rebuild record with a RAID-level decision note (Domain 1); a directory-plus-DNS/DHCP build note verified against the lab domain (Domain 2); a hardening-and-verified-restore record with a Lynis score and RTO/RPO note (Domain 3); or a completed seven-step troubleshooting runbook for a self-inflicted service failure (Domain 4).
A plain-language explanation of the concept, the redundancy or least-privilege or recovery principle it demonstrates, the tool and step chosen, what a defender or administrator should do next, and the condition that would change the answer — plus, for hardware, an honest note of what the free software lab could not show.
All authored checks for the domain attempted, with each miss corrected against its cited source and re-applied to a fresh scenario, plus a recorded snapshot-and-revert confirmation for every lab that built, hardened, or broke a system.
After a missed check
Identify whether the question tests server hardware and storage, server administration and services, security and disaster recovery, or troubleshooting methodology before reviewing the answer.
Write why the distractor was plausible and which RAID/redundancy fact, service-dependency or storage/HA choice, hardening/backup/recovery principle, or troubleshooting-methodology step distinguishes the correct answer.
Change one detail — the RAID level and disk count, the service or its dependency, the backup type or recovery objective, or the fault symptom — and explain whether the correct answer changes.
Completing this policy demonstrates current-objectives Server+ coverage and hands-on server-administration practice inside RoleMath on VMs you own; it does not predict an exam score, establish professional server-administration experience, satisfy CompTIA's recommended two years of hands-on experience, or serve as a RoleMath credential.
Integrated practice
Integrated server build: stand up, harden, back up, and troubleshoot a small server on your own isolated lab
Integrate all four SK0-005 domains into one reviewable evidence packet by building a small server on VMs you own — install the operating system and a role with storage, harden it, back it up with a verified restore, then diagnose and fix an injected fault with the seven-step methodology — documenting throughout and reverting every VM when finished.
Workflow
Snapshot a fresh server VM you own on an isolated Host-Only network, then provision storage (Domain 1): add virtual disks and build a software-RAID array (or document the RAID-level choice and its capacity/fault-tolerance trade-off), noting what a hardware RAID controller would add that the VM cannot show.
Install and configure a server operating system and a real role with the storage attached (Domain 2) — for example a Linux server with a file share on the RAID volume, or the Windows Server Evaluation promoted to a lab domain controller with DNS and a DHCP scope — confining everything to the fictional lab domain and network.
Harden the server (Domain 3): enable automatic security updates, apply a default-deny firewall allowing only what the role needs, disable direct root/administrator remote login where applicable, create a least-privilege administrative account, and audit the baseline (Lynis on Linux) — recording the score and top remaining items.
Back up the server's data and configuration with a 3-2-1-aware copy to a separate location, then simulate data loss by deleting a file and successfully restore it, recording the RTO/RPO reasoning and confirming the restore actually returned the data.
Inject a controlled, reproducible fault into the running role (Domain 4) — for example an invalid configuration line that stops the service — recording the symptom and what changed as step one of the methodology.
Walk CompTIA's seven-step troubleshooting methodology against the injected fault: identify the problem, form and test a theory using status/config-test/journal tools, plan and implement the fix, verify full functionality, and document findings, actions, and outcomes in the runbook.
Run the wider operational checks (failed units, disk space, recent errors) to build the habit of looking past the immediate fault, and record anything they surface.
Write an integrated build-and-recovery report — a build summary, the hardening baseline, the verified backup-and-restore drill, and the completed seven-step troubleshooting runbook — using fictional lab details only.
Run the cleanup: stop any arrays and services touched, remove sample data and backups, revert every VM to its pre-lab snapshot, and verify nothing persists in the lab.
Crosswalk every artifact to the four SK0-005 domain IDs, diff the current CompTIA objectives, flag any uncovered topics as explicit gaps, and record the next server or exam-scheduling decision rather than inferring a pass from coverage.
Retained artifacts
A storage-and-hardware record: the software-RAID build (or documented RAID-level choice) with a capacity/fault-tolerance note and what a hardware controller would add
A build note for the operating system and role stood up with storage attached, verified and confined to the fictional lab domain and isolated network
A hardening record: automatic updates, default-deny firewall, disabled remote root/admin login, a least-privilege account, and a recorded audit score
A backup-and-restore record: a 3-2-1-aware copy, a deleted-then-restored file confirmed back in place, and a short RTO/RPO note
A completed seven-step troubleshooting runbook for the injected fault plus captured wider-check output, and an integrated build-and-recovery report with a four-domain crosswalk, an objectives diff, and a snapshot-revert confirmation
Review checklist
The build, hardening, backup, and troubleshooting steps describe one consistent server lifecycle run entirely on virtual machines the learner owns on an isolated Host-Only network, with a snapshot taken before and every VM reverted afterward.
The storage step reasons correctly about the RAID level's usable capacity and fault tolerance, and the honest gap between software RAID and a hardware controller is stated rather than glossed over.
The hardening step applies a default-deny firewall, disables direct remote root/administrator login where applicable, uses a least-privilege account, and records an audit baseline — not just a partial or cosmetic change.
The backup was actually test-restored: a deleted file was confirmed back in place, with RTO/RPO reasoning recorded, so the backup is demonstrated rather than assumed.
The troubleshooting runbook documents all seven methodology steps in order for a self-inflicted fault, localizes the exact cause, verifies the service is active, and includes the documentation step the methodology explicitly rewards.
The report uses fictional lab details only, no real credentials, hostnames, or personal data appear anywhere, and the lab domain never touched a real production domain or network.
The current CompTIA Server+ objectives were rechecked and any changed objective, weight, or exam code invalidates the affected mapping or review.
All four current SK0-005 domains map to at least one artifact; uncovered topics remain explicit gaps rather than implied completion.
The packet does not claim exam success, official CompTIA approval or training beyond linked sources, professional server-administration experience, satisfaction of CompTIA's recommended experience, or a RoleMath credential.
Safety boundary: Run the entire capstone ONLY on virtual machines you own on your own hardware on an isolated Host-Only network — never a physical server, a production or shared machine, or any system you do not own, and never over a Bridged adapter. Snapshot every VM before you start and revert it afterward, keep the lab domain and all identities fictional with throwaway passwords and sample data, note that the Windows Server Evaluation is disposable and expires after 180 days, and treat the destructive storage commands and the deliberate service break as safe only inside a disposable snapshotted VM.
Finish honestly
Completion, portfolio, and maintenance
Completion evidence
All four current SK0-005 domain modules have been covered and checked against the official CompTIA Server+ objectives, including a recheck of the current objectives before any exam scheduling.
Every domain lab has been run only on virtual machines the learner owns on an isolated Host-Only network — with a snapshot taken before and every VM reverted to its pre-lab snapshot afterward — and its labeled artifact retained.
Every authored knowledge check has been attempted and each miss has a cited correction plus a fresh scenario, with the heaviest domain (administration, 30%) and troubleshooting (28%) given proportionate study time.
The CompTIA objectives and the free virtualization, server-OS, and community resources have been used within their current free-access terms, with the Windows Server Evaluation's 180-day expiry noted and any community tutorial reconciled to the official objectives.
The integrated capstone passes its build, hardening, verified-restore, troubleshooting-methodology, consistency, isolation, and four-domain coverage review, with nothing left in the lab.
The learner has recorded remaining objective gaps and a next server or exam-scheduling decision; completion is not represented as an exam result, a credential, professional server-administration experience, satisfaction of CompTIA's recommended experience, or job readiness.
Portfolio candidates
A storage record: a software-RAID build-fail-rebuild log (or documented RAID-level choice) with a capacity/fault-tolerance note and the hardware-controller gap
A server build note: the operating system and role stood up with storage attached, verified and confined to a fictional lab domain on an isolated network
A hardening record: automatic updates, a default-deny firewall, disabled remote root/admin login, a least-privilege account, and a recorded audit score
A backup-and-restore record: a 3-2-1-aware copy, a deleted-then-restored file confirmed back, and a short RTO/RPO note
A completed seven-step troubleshooting runbook for a self-inflicted service fault, with the exact cause localized and the fix verified
The integrated capstone build-and-recovery report with a four-domain crosswalk, an objectives diff, and a snapshot-revert confirmation
Present the packet as self-directed Server+ lab work done only on virtual machines you own on an isolated network. Do not call it production server administration, CompTIA approval, professional server-administration experience, satisfaction of CompTIA's recommended two years of experience, or a RoleMath credential, and never publish real hostnames, credentials, or data.
Freshness controls
Objective source checked 2026-07-10. Recheck objectives every 30 days and resources every 90 days.
Stop and re-verify when
CompTIA changes the Server+ objectives, domain set, weight ranges, exam code, format, passing score, lifecycle, recommended experience, or credential terms (including the Continuing Education renewal model).
A free tool or operating system the labs rely on (VirtualBox, mdadm, UFW, unattended-upgrades, OpenSSH, rsync, Lynis, nginx, systemd tooling, Ubuntu Server, Rocky Linux, or the Windows Server 2022 Evaluation) changes URL, access, version, behavior, its free tier, or its reuse terms.
The Windows Server 2022 Evaluation changes its free-download terms, account requirement, or 180-day evaluation window, or a successor Windows Server evaluation replaces it.
A lab can no longer be run isolated on a self-owned VM within the free tier, or its snapshot-and-revert, Host-Only isolation, fictional-identity, or destructive-command-safety guarantees no longer hold.
A server-hardware, administration, security-and-disaster-recovery, or troubleshooting concept materially changes, or a topic is added to or removed from the objectives.
Any module, lab, check, phase, capstone step, account instruction, safety guardrail, or objectives diff fails technical, source, server-domain, intermediate-level, safety, privacy, accessibility, currency, or claims review.
For Server+ we recommend studying the domains in their published order, because that order builds from the physical foundation upward and each domain gives you the vocabulary and the running systems the next one needs. CompTIA weights the four domains as Server hardware installation and management 18%, Server administration 30%, Security and disaster recovery 24%, and Troubleshooting 28%, so the heaviest single domain is administration and the second heaviest is troubleshooting — and studying in published order still serves you well. We open with Server hardware installation and management (Domain 1) even though at 18% it is the lightest slice, because it is the physical foundation: racks, power and cooling redundancy, storage and RAID, firmware and out-of-band management are the layer every server sits on, and you cannot meaningfully install an operating system until you understand the hardware and storage beneath it. Server administration (Domain 2) comes next and deserves the most study time because at 30% it is the heaviest domain on the exam: it spans operating-system installation, core network services (DNS, DHCP, NTP, directory), storage services, high availability, virtualization, scripting, asset management, and licensing — the day-to-day of running servers, and the domain whose labs stand up the systems you will later secure and troubleshoot. Security and disaster recovery (Domain 3, 24%) follows because it protects what you just built: data security, identity and access management, hardening, patch and vulnerability management, decommissioning, backup strategy, and disaster-recovery planning only make sense once there are running services to defend and back up. Troubleshooting (Domain 4) comes last, and at 28% it is the second-heaviest domain, so it earns substantial study time — but it belongs at the end because it synthesizes everything before it: applying CompTIA's structured methodology to hardware failures, storage problems, operating-system and service faults, network connectivity, and security issues requires that you already understand the hardware, the administration, and the security layers you are diagnosing. In short: build the hardware foundation, learn to administer and run the services, secure and back them up, and only then practice diagnosing the whole stack — giving Domain 2 the most study time as the heaviest domain and Domain 4 close behind. This is sequencing advice based on the published weights and how the material builds, not a claim about the science of learning — if a different order fits how you think, use it.
Study this first. At 18% it is the lightest domain by weight, but it is the physical foundation the rest of the certification sits on: racks, power and cooling, storage and RAID, firmware, and out-of-band management are the layer every operating system and service depends on. Master the hardware vocabulary before you install anything.
This is the 'the physical box and the storage beneath the operating system' domain, and CompTIA weights it at 18% of the exam. It is the lightest domain by raw weight, but we study it first because it is the foundation everything else rests on: you cannot sensibly install a server operating system, plan storage services, or reason about high availability until you understand the hardware, the power and cooling that keep it running, and the storage layer that holds its data. Server hardware is where the physical reality of running infrastructure lives, and the exam expects you to reason about it like someone who has actually racked and cabled a machine.
The physical installation and power side is the first pillar. Servers live in racks measured in rack units (U), mounted with rails, and cabled for both data and power. Power is deliberately redundant in real data centers: dual power supplies fed from separate circuits, power distribution units (PDUs) in the rack, and uninterruptible power supplies (UPS) that ride through outages and allow a graceful shutdown. Cooling and environmental control matter just as much — servers generate significant heat, and the exam expects you to understand airflow (hot aisle / cold aisle), temperature and humidity monitoring, and why environmental failure is as dangerous as a component failure. The recurring theme is redundancy and resilience: a professional designs so that a single power feed, fan, or supply failing does not take the server down.
Storage is the heaviest technical topic in this domain, because a server is largely defined by how it stores and protects data. You should know the common drive interfaces and their trade-offs — SATA (cheap, slower), SAS (enterprise, dual-ported, higher performance), and NVMe (flash over PCIe, the fastest) — and the role of host bus adapters (HBAs) and RAID controllers. RAID is central and examinable: RAID 0 stripes for speed with no redundancy, RAID 1 mirrors for redundancy, RAID 5 stripes with distributed parity (survives one disk loss), RAID 6 adds a second parity (survives two), and RAID 10 combines mirroring and striping for both performance and redundancy. You should be able to reason about usable capacity, fault tolerance, and rebuild behavior for each level, and understand hot-swap drives and hot spares that let a failed disk be replaced without downtime.
Firmware and out-of-band management are the third pillar and are easy to underestimate. Every server has firmware — the BIOS or UEFI that initializes hardware, plus firmware on RAID controllers, network adapters, and drives — and keeping it at a known, tested baseline is part of responsible server management. Out-of-band management is what lets an administrator control a server that is powered off or unresponsive: a dedicated management controller (a baseboard management controller, or BMC) exposed through vendor interfaces like Dell iDRAC or HPE iLO, giving remote power control, a virtual console, and hardware health telemetry over a separate network path. The exam expects you to know that this management plane exists, why it is kept on an isolated network, and what it lets you do that the operating system cannot.
Tying the domain together is a management-and-documentation mindset. Good server hardware practice is not just assembling a machine — it is labeling, cable management, asset tracking, firmware baselines, and monitoring hardware health (drive SMART status, fan and power telemetry, RAID array state) so that problems are caught before they become outages. This is also where the honest free-study caveat for Server+ starts to bite: hardware is the topic the free ecosystem covers least well, because you cannot cheaply own a rack, a UPS, or a hardware RAID controller. The realistic free substitute is software RAID in a virtual machine plus vendor documentation for the physical specifics, which is exactly what the lab below does.
Study this domain by doing the storage concepts hands-on with free software RAID and reading vendor documentation for the physical hardware you cannot own, because that is the honest free path. The lab below has you add four virtual disks to an Ubuntu Server VM and use mdadm to create a RAID 1 mirror, deliberately fail and rebuild it, and create a RAID 5 array — learning the redundancy, degraded-state, and rebuild behavior the exam tests. Be clear-eyed about the limit: VirtualBox cannot emulate a hardware RAID controller, so software RAID teaches the concepts while you supplement the controller specifics with HPE and Dell documentation. As always, read the official Server+ objectives for CompTIA's authoritative topic list; this explanation paraphrases its scope in our own words rather than reproducing it.
Learn it free
Official · Official exam objectives
CompTIA Server+ (SK0-005) exam objectivesThe exam's own topic list for this domain's hardware, storage, and RAID coverage — the scope anchor to read directly, because Server+ has no free video course to lean on. (captured 2026-07-10)
VirtualBox (free virtualization)The free hypervisor that hosts the Ubuntu Server lab VM; note it cannot emulate a hardware RAID controller, so software RAID teaches the concepts and vendor docs cover the controller specifics. (captured 2026-07-10)
Serverplus Raid Lab
Create a RAID 1 mirror with mdadm, fail a member, and rebuild the array on disks you own Create a RAID 5 array and reason about usable capacity, fault tolerance, and rebuild behavior
Free tools
VirtualBox on your own hardware
Ubuntu Server guest VM with four added virtual disks
Steps
Snapshot the Ubuntu Server VM, add four small virtual disks in VirtualBox Settings > Storage, then confirm inside the VM that the four empty disks are visible and install mdadm.
Create a RAID 1 mirror across two of the disks, watch the resync, format and mount it, and write a test file so you have data on the array to protect.
Deliberately fail a mirror member, confirm the array is DEGRADED but the data survives, then remove the failed disk and add a replacement and watch the rebuild.
Starting from a fresh VM snapshot (so the disks are free — sdb is still an active member of the RAID 1 array from the previous step), create a RAID 5 array across three disks and note that usable capacity is (n-1) disks and it survives a single disk loss, then read HPE/Dell controller documentation to note what a hardware RAID controller adds that software RAID in a VM cannot show.
Record which RAID level you would choose for a given goal and why, then unmount and stop the arrays, zero the superblocks, and revert the VM to its pre-lab snapshot.
What you should see
Confirm the saved output shows a RAID 1 array that went clean, degraded (after a failed member, data intact), and rebuilt, plus a RAID 5 array with correct usable capacity, and that a RAID-level decision note and hardware-controller-gap note were recorded.
Practice evidence maps to exam_domain_comptia_server_plus_sk0_005_01
Stay safe & legal: Run every command only inside a virtual machine you own on your own hardware, against the empty virtual disks you added for this lab; never run mdadm against a physical machine or any disk holding data you care about, because these commands are destructive to their target disks by design. Account required: no; payment required: no; maximum designed cost: $0.
Check yourself
3RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 2 of 4 · domain 2 · 30% of the exam
Server administration
Study this second, and give it the most time — at 30% it is the heaviest domain on the exam. It spans operating-system installation, core network services, storage services, high availability, virtualization, scripting, asset management, and licensing: the day-to-day of actually running servers, and the labs here stand up the systems you will later secure and troubleshoot.
This is the 'actually run the server' domain, and at 30% it is the single heaviest slice of the exam — nearly a third of it — so it deserves the most study time on the track. Server administration is the day-to-day work of installing operating systems, standing up the network services an organization depends on, provisioning storage, keeping services available, virtualizing workloads, and documenting and licensing it all. The labs in this domain build the running systems that the security and troubleshooting domains later defend and diagnose, which is another reason it comes second in the sequence: everything downstream needs the services you learn to run here.
Operating-system installation and configuration is the foundation. You should understand installing and configuring both Windows Server and common Linux server distributions, and the automation that makes installation repeatable at scale — unattended installations and network-based provisioning such as PXE boot. Beyond the initial install, administration means configuring the server's identity, network settings, roles, and services, and doing it consistently. The exam expects you to reason about the right operating system and configuration for a described workload, and to know that a hand-installed one-off server does not scale — automation and standardization are professional practice.
Network services are the heart of what a server actually provides. Core services on the blueprint include DNS (name resolution), DHCP (address assignment), NTP (time synchronization, which quietly underpins authentication and logging), and directory services (centralized identity, such as Active Directory). You should also understand VLANs and how servers sit on segmented networks, and NIC teaming, which bonds multiple network interfaces for redundancy and throughput. These services are what turn a bare operating system into infrastructure, and configuring them correctly — and understanding how they depend on each other, such as directory services relying on DNS and NTP — is exactly what the domain's performance-based questions probe.
Storage services, high availability, and virtualization are the next cluster of topics, and they are heavily weighted. Storage services cover presenting storage to clients and servers — iSCSI (block storage over IP), NFS and SMB (file shares), and logical unit numbers (LUNs) carved from shared storage. High availability covers keeping services running through failure: clustering, load balancing, replication, and failover, along with the concepts of redundancy and fault tolerance at the service level. Virtualization is central to modern server administration: Type-1 (bare-metal) hypervisors, the virtual-machine lifecycle, resource allocation, and increasingly containers as a lighter-weight way to package and run workloads. The exam expects you to recognize each of these and match a technology to a described availability or storage goal.
Rounding out the domain are scripting, asset management, documentation, and licensing — the operational discipline that keeps a server estate manageable. Scripting (PowerShell on Windows, Bash on Linux) is how administrators automate repetitive configuration and reporting rather than clicking through every task by hand. Asset management and documentation track what hardware and software exist, their configurations, and their lifecycle, so that changes are controlled and audits are possible. Licensing — understanding per-core, per-socket, per-user, and subscription models — is a genuinely examinable topic because getting it wrong is expensive and non-compliant. The unifying theme is that administration is not just making a service work once; it is running it repeatably, documenting it, and staying compliant.
Study this domain by standing up real network services on a free evaluation server, because that hands-on configuration is exactly what the heaviest domain rewards. The lab below has you install the free Windows Server 2022 Evaluation, promote it to a domain controller, add DNS and DHCP, and create an organizational unit, a user, and a security group — building the directory-plus-core-services stack the domain centers on. Be aware of the honest limit: the evaluation is free but time-boxed to 180 days, so note the expiry and treat the VM as disposable. Free Linux server options — Ubuntu Server and Rocky Linux — cover the Linux side of the same skills at no cost. As always, read the official Server+ objectives for CompTIA's authoritative topic list; this explanation paraphrases its scope in our own words rather than reproducing it.
Learn it free
Official · Official exam objectives
CompTIA Server+ (SK0-005) exam objectivesThe authoritative topic list for this heaviest domain's administration, services, storage, HA, virtualization, scripting, and licensing coverage — read it directly, because no free video course covers Server+ end to end. (captured 2026-07-10)
Official · Free official evaluation software
Windows Server 2022 Evaluation (free 180-day)The free (but time-boxed to 180 days) evaluation this domain's lab uses to build a domain controller with DNS and DHCP; note the expiry and treat the VM as disposable. (captured 2026-07-10)
Official · Free official server OS
Ubuntu Server (free download)A free, no-expiry Linux server operating system for practicing the Linux side of installation, services, and storage the domain covers. (captured 2026-07-10)
Official · Free official server OS
Rocky Linux (free download)A free, enterprise-compatible Linux server distribution for practicing RHEL-family administration and services at no cost. (captured 2026-07-10)
Serverplus Roles Lab
Install Windows Server and promote it to a domain controller with DNS on an isolated lab network Configure a DHCP scope and create a directory OU, user, and security group
Free tools
VirtualBox on your own hardware
Windows Server 2022 Evaluation guest VM on an isolated Host-Only network
Steps
Install the free Windows Server 2022 Evaluation in a VirtualBox VM on an isolated Host-Only network, note the 180-day expiry, snapshot the VM, then set a static IP, point DNS at the server itself, rename it, and reboot.
Install the AD DS, DNS, and DHCP roles with their management tools.
Promote the server to a new forest for an isolated lab domain, supplying a Directory Services Restore Mode password when prompted, and reboot.
Authorize DHCP and create an address scope, then create an organizational unit, a user, and a security group, and add the user to the group.
Verify the domain, DHCP scope, and DNS resolution, record the results as evidence, then revert the VM to its pre-lab snapshot rather than uninstalling.
What you should see
Confirm the saved output shows a promoted labdomain.local domain controller with integrated DNS, an active DHCP scope, working name resolution, and a created OU/user/security group with correct membership, all on an isolated Host-Only network.
Practice evidence maps to exam_domain_comptia_server_plus_sk0_005_02
Stay safe & legal: Build and promote the lab domain only inside a virtual machine you own on your own hardware, on an isolated Host-Only network; never join, promote against, or touch a real production domain, and keep the domain name confined to a fictional lab (labdomain.local). Account required: yes; payment required: no; maximum designed cost: $0.
Check yourself
3RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 3 of 4 · domain 3 · 24% of the exam
Security and disaster recovery
Study this third, after you can administer servers. At 24% it is a substantial domain, and it protects what you just built: data security, identity and access, hardening, patch and vulnerability management, decommissioning, backup, and disaster-recovery planning only make sense once there are running services to defend and back up.
This is the 'protect the servers and be ready when things fail' domain, and CompTIA weights it at 24% of the exam — a substantial slice. Security and disaster recovery sits after administration in the sequence for a reason: you cannot meaningfully secure, harden, back up, or plan the recovery of services that do not exist yet. This domain takes the running systems you learned to administer and adds the discipline that keeps them confidential, controlled, patched, recoverable, and safely retired. It spans two related halves — security (protecting the running server) and disaster recovery (getting back to running after a failure) — and the exam tests both.
Data security and access control are the first pillar. You should understand encryption both at rest (protecting stored data on disks and backups) and in transit (protecting data moving over the network), and data classification that decides how strongly each kind of data must be protected. Identity and access management is central: role-based access control (RBAC), the principle of least privilege (grant only the access a role needs), and multi-factor authentication (MFA) for stronger sign-in. Physical security belongs here too — locked racks, restricted data-center access, and the reality that an attacker with physical access to a server has a much larger attack surface. The recurring exam theme is minimizing what each account and each person can reach.
Server hardening and patch management are the operational core of the security half. Hardening reduces a server's attack surface: turning off unnecessary services and ports, enforcing a host firewall with a default-deny posture, disabling risky defaults (such as direct root login), enabling secure boot, and applying a security baseline consistently. Patch and vulnerability management is the ongoing side — knowing what is installed, tracking vulnerabilities, testing and applying patches on a controlled schedule, and understanding the tension between patching quickly for security and testing changes to avoid breaking production. The exam expects you to reason about a defensible patch process and about which hardening steps most reduce risk for a described server.
Decommissioning and data sanitization close the security half and are easy to overlook. When a server or drive reaches end of life, the data on it must be destroyed so it cannot be recovered — through secure wiping, cryptographic erasure, degaussing, or physical destruction appropriate to the media and the data classification. Simply deleting files or reformatting is not sanitization. This is a genuinely examinable topic because improper decommissioning is a common, expensive data-breach cause: an organization can do everything else right and still leak sensitive data by selling or discarding a drive that was never properly wiped.
The disaster-recovery half turns protection into resilience. Backup strategy is central and examinable: full, incremental, and differential backups and their trade-offs in backup time versus restore complexity; the widely-taught 3-2-1 rule (three copies, on two different media, with one off-site); and — crucially — that a backup you have never test-restored is not a backup you can trust. Recovery objectives frame the planning: the recovery time objective (RTO, how quickly you must be back) and the recovery point objective (RPO, how much data you can afford to lose). Disaster recovery and business continuity planning cover failover, alternate sites, runbooks, and regular testing. The professional lesson the exam rewards is that recovery is planned and tested in advance, not improvised during an outage.
Study this domain by hardening a server you own and running a real backup-and-restore drill, because both are hands-on skills the exam treats as core. The lab below has you harden an Ubuntu Server VM — enabling automatic security updates, setting a default-deny firewall, disabling root SSH login, creating a least-privilege administrative user, and auditing the result with Lynis — and then run a 3-2-1-aware backup, simulate data loss, and restore it, proving the backup actually works. The free Linux server operating systems make all of this achievable at no cost. As always, read the official Server+ objectives for CompTIA's authoritative topic list; this explanation paraphrases its scope in our own words rather than reproducing it.
Learn it free
Official · Official exam objectives
CompTIA Server+ (SK0-005) exam objectivesThe authoritative topic list for this domain's security, hardening, patch, backup, and disaster-recovery coverage — the scope anchor to read directly, since Server+ has no free video course. (captured 2026-07-10)
Official · Free official server OS
Ubuntu Server (free download)The free, no-expiry Linux server this domain's hardening and backup lab runs on, so the hands-on security work costs nothing. (captured 2026-07-10)
Official · Free official server OS
Rocky Linux (free download)A free enterprise-compatible Linux server for practicing the same hardening and backup discipline on the RHEL family at no cost. (captured 2026-07-10)
Serverplus Hardening Backup Lab
Harden an Ubuntu Server VM with a default-deny firewall, no root SSH, and least-privilege access Run a 3-2-1-aware backup, simulate data loss, and successfully restore it to prove the backup works
Free tools
VirtualBox on your own hardware
Ubuntu Server guest VM you own
Steps
Snapshot the VM, patch the baseline, and enable automatic security updates so the server stays current without manual intervention.
Set a default-deny inbound firewall allowing only SSH, then disable direct root SSH login and restart the SSH service.
Create a least-privilege administrative user in the sudo group, then run a Lynis audit and record the hardening score and top remaining suggestions.
Create sample config data, make a full rsync copy to a separate directory (the 3-2-1 mindset), delete a file to simulate data loss, restore it from the backup, and confirm it returns.
Record the RTO/RPO reasoning for this drill (how quickly you restored and how much data a real incident could have lost), then revert the VM to its pre-lab snapshot.
What you should see
Confirm the saved evidence shows automatic security updates enabled, a default-deny firewall allowing only SSH, root SSH login disabled, a least-privilege sudo user, a recorded Lynis score, and a completed backup drill where a deleted file was successfully restored from a separate copy.
Practice evidence maps to exam_domain_comptia_server_plus_sk0_005_03
Stay safe & legal: Apply every hardening and backup command only inside a virtual machine you own on your own hardware, snapshotted beforehand; never run these firewall, SSH, or update changes against a machine you depend on or do not own. Account required: no; payment required: no; maximum designed cost: $0.
Check yourself
3RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 4 of 4 · domain 4 · 28% of the exam
Troubleshooting
Study this last, but give it real time — at 28% it is the second-heaviest domain. It belongs at the end because it synthesizes everything before it: applying CompTIA's structured methodology to hardware, storage, operating-system, network, and security problems requires that you already understand the layers you are diagnosing.
This is the 'something is broken — find and fix it, methodically' domain, and at 28% it is the second-heaviest slice of the exam, so it earns substantial study time even though it comes last in the sequence. Troubleshooting belongs at the end because it synthesizes every prior domain: you cannot diagnose a degraded RAID array without the hardware knowledge from Domain 1, a failed service without the administration knowledge from Domain 2, or a security-related fault without the security knowledge from Domain 3. This domain is less about memorizing new facts and more about applying a disciplined process to the systems you already understand.
The structured methodology is the spine of the domain and is directly examinable. CompTIA teaches a repeatable, seven-step troubleshooting process: identify the problem (and what changed), establish a theory of probable cause (questioning the obvious first), test the theory, establish a plan of action considering the impact, implement the solution or escalate, verify full functionality and apply preventive measures, and document findings, actions, and outcomes. The exam rewards choosing the methodical next step over guessing, and it frequently tests whether you follow the process in order — for example, that you verify functionality and document after a fix rather than walking away. Internalizing this process is the single highest-value thing you can do for this domain.
Hardware and storage troubleshooting apply the methodology to the physical layer. Hardware problems show up as power failures, POST errors, diagnostic LEDs and beep codes, overheating, and failed components, and the tester reads those signals to localize the fault. Storage problems are a major sub-topic given how central storage is to a server: a degraded or failed RAID array (and the difference between a survivable degraded state and actual data loss), disk failures and rebuilds, and connectivity problems in networked storage such as iSCSI path or multipath failures. The exam expects you to reason from a symptom — a blinking drive LED, a degraded array, a storage target that suddenly cannot be reached — to a probable cause and a safe corrective action.
Operating-system, software, and service troubleshooting is where a great deal of real day-to-day server work lives, and it maps directly to the administration domain. This includes boot failures, services that will not start or that crash, resource exhaustion (a full disk, memory pressure, runaway processes), and configuration errors. The core skill is log analysis: reading service status, system logs, and journals to find the exact error rather than guessing — on Linux, tools like 'systemctl status', 'journalctl', and service-specific config tests; on Windows, the Event Viewer and service management. A tester who can read a failed service's logs and find the one bad configuration line is doing exactly what this domain rewards.
Network and security troubleshooting round out the domain. Network problems include connectivity failures, name-resolution (DNS) issues, misconfigured IP or routing, firewall rules blocking legitimate traffic, and NIC or teaming faults — and here the skill is working methodically up and down the stack from physical link to application. Security-related problems include access and permission failures, certificate and authentication issues, and the security implications of a misconfiguration. Across all of these, the unifying discipline is the same: form a theory, test it with a specific command or check, and confirm the fix — and then, crucially, document what happened so the same problem is faster to solve next time and preventive measures can be put in place.
Study this domain by deliberately breaking a service on a server you own and diagnosing it with the seven-step methodology, because the process is exactly what the exam tests. The lab below has you break an nginx service with a bad configuration line, then walk the methodology — reading 'systemctl status', running 'nginx -t' to find the exact bad line, checking 'journalctl' — restore it, and verify it is active, plus build the habit of wider checks like 'systemctl --failed' and 'df -h'. It runs on the free Ubuntu Server VM you already have, so it costs nothing. As always, read the official Server+ objectives for CompTIA's authoritative topic list; this explanation paraphrases its scope in our own words rather than reproducing it.
Learn it free
Official · Official exam objectives
CompTIA Server+ (SK0-005) exam objectivesThe authoritative topic list for this second-heaviest domain's methodology and hardware/storage/OS/network/security troubleshooting coverage — read it directly, since Server+ has no free video course to walk it. (captured 2026-07-10)
Official · Free official server OS
Ubuntu Server (free download)The free, no-expiry Linux server the break/fix troubleshooting drill runs on, so practicing the methodology hands-on costs nothing. (captured 2026-07-10)
Official · Free lab tooling
VirtualBox (free virtualization)The free hypervisor whose snapshot feature makes it safe to deliberately break and restore a service while practicing the methodology. (captured 2026-07-10)
Serverplus Troubleshooting Lab
Diagnose a deliberately-broken service using CompTIA's seven-step troubleshooting methodology Read service status, config tests, and journals to localize a fault and verify the fix
Free tools
VirtualBox on your own hardware
Ubuntu Server guest VM you own
Steps
Snapshot the VM, install and start nginx, confirm it serves a baseline page, and back up its config so you can restore it later.
Deliberately break the service by appending an invalid line to the nginx configuration and restarting it so it fails to start — a controlled, reproducible fault.
Walk methodology steps 1-3: read the service status, run the config test that points at the exact bad line, and check the journal for the error, filling in the runbook as you form and test a theory.
Walk methodology steps 4-6: restore the backed-up config, re-test it, restart the service, and verify it is active, then document findings, actions, and outcomes in the runbook (step 7).
Build the wider-check habit by running systemctl --failed, df -h, and a recent-errors journal check, then optionally repeat the drill on another service and revert the VM to its pre-lab snapshot.
What you should see
Confirm the runbook documents all seven methodology steps for a self-inflicted nginx failure, that nginx -t localized the bad line, that the service was restored to active, and that the wider checks (systemctl --failed, df -h) were run and captured.
Practice evidence maps to exam_domain_comptia_server_plus_sk0_005_04
Stay safe & legal: Deliberately break and repair the service only inside a virtual machine you own on your own hardware, snapshotted beforehand; never induce a fault on a machine anyone depends on or that you do not own. Account required: no; payment required: no; maximum designed cost: $0.
Check yourself
3RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Skills you’ll build
Studying CompTIA Server+builds transferable skills that carry across employers and platforms, not just toward this one exam. Each has a free, source-cited RoleMath primer — what it is, a step-by-step free learning path, clearly labeled free resources, and a safe hands-on exercise:
Work through the modules above, then get a personalized read on where you stand: the readiness check maps your background against these same published domains and suggests what to study first — no score, no pass prediction.
Exam registration fee: Approximately $390 USD for the SK0-005 exam (verify the current price on CompTIA's official page before registering; regional prices vary). Official CompTIA Server+ certification page
Exam format: Multiple-choice and performance-based questions. Verify the current question count, time limit, and passing score on CompTIA's official exam page before your exam. Official CompTIA Server+ certification page
Renewal: SK0-005 certifications earned on or after 2025-10-01 use CompTIA's Continuing Education (CE) model and must be renewed every three years with continuing-education units (a change from the earlier Good-for-Life status). Official CompTIA Server+ certification page
Recommended experience: CompTIA recommends roughly two years of hands-on server experience plus A+/Network+ level knowledge. A determined learner without that can still study the free path, but should expect to build the underlying hardware and networking fundamentals along the way. Official CompTIA Server+ certification page
Version currency: SK0-005 is current; no successor exam is announced as of 2026-07-10. Verify the current version on CompTIA's page before studying. Official CompTIA Server+ certification page
A free, source-cited study companion built on CompTIA's published Server+ (SK0-005) exam objectives — not official training, not a pass guarantee. Server+ has a thinner free ecosystem than A+ or Network+: there is no free Professor Messer course and no free CertMaster trial for it, so the honest free path is the official objectives as your scope anchor plus a hands-on lab you build yourself from free virtualization and free server operating systems. Every lab here runs only on virtual machines you own on your own hardware; snapshot before you start and revert afterward. Verify the current objectives on the official page before your exam.
Certification and vendor names are used only to identify the program this independent study companion refers to. RoleMath is not affiliated with, endorsed by, or sponsored by CompTIA.