Skip to content
Français
Account: not signed in, sync available My learning
Select theme
Français

Validate your Linux skills

By updated

Improve this page

This page explains how to prove what you can do on Linux. The course does not stop at guides to read: every skill is demonstrated on a real machine, through a lab, a timed drill or a capstone, and an automatic score confirms that the operation worked. You will find the three tests that close each level, the RHCSA and LFCS mock exams, and the map of the lab catalogue.

What you will learn

  • Tell apart a lab, a drill, a capstone and a mock exam.
  • Pick the test that closes your level: L1, L2 or L3.
  • Start a mock exam or a capstone with the dsoxlab CLI.
  • Read the map of the lab catalogue, level by level.

How does validation work?

The linux-dsoxlab-training catalogue holds 86 labs, and each one is wired into the guide that teaches it: the guide gives the context, the lab provides the proof of execution. The dsoxlab CLI starts them on AlmaLinux 10 and Ubuntu 24.04 virtual machines, then reads the observable state of the system, never the commands you typed. Validation rises in difficulty by steps:

  1. Lab: one skill, one exercise, one automatic check.
  2. Drill: one domain under exam conditions, timed, with no hints.
  3. Capstone: a scenario that combines several domains in a realistic case.
  4. Mock exam: a full simulation of a certification, within a time limit.

What are the four forms of validation?

Each form answers a different question, and that is what guides the choice. The lab checks that you can perform a gesture, the drill that you do it fast and without help, the capstone that you can combine several gestures to deliver or repair a server, and the mock exam that you can hold the format of a certification.

Labs

One lab per skill, sorted by level: l1 for the fundamentals, l2 for users, packages and storage, l3 for boot, services and scheduling, l4 for networking, firewall, SELinux and containers. Six lfcs labs cover what is specific to Debian and Ubuntu.

Drills

Nine short tests by domain: essential commands, users and groups, packages, storage, networking, firewall, systemd, SELinux, AppArmor. No hints, a stopwatch.

Capstones

Two synthesis scenarios: put a server into production, and repair a server whose symptom says nothing. The machine reboots before scoring.

Mock exams

The EX200 (RHCSA on RHEL 10) in 20 tasks on 2 VMs, and the LFCS in 17 tasks on Ubuntu 24.04, scored out of 100 points with 70 to pass.

What ends each of the three levels?

A level without a finish line is not a level, it is a shelf. The course counts more than 200 lessons: what was missing was not content, it was the ability to say "I have finished that one". The three tests below already existed, and they have carried a level name since 15 September 2026.

LevelWhat you can claimThe test that proves it
L1, useI work alone on a Linux machine without breaking itdrill-essential-commands: 5 tasks, 20 minutes, no hints
L2, administerI put a server into service and make it persistentcapstone-mise-en-production: 9 deliverables, and the machine reboots
L3, operateI take over an unknown or broken machine, understand its state and restore the servicecapstone-serveur-casse: one hidden fault among six

These three tests are not courses. They are measurements, and they read in this order: use a machine, deliver one, recover one. The certifications sit on top of them and do not replace this progression.

The L1 test opens the series: five tasks, twenty minutes, no hints. It asks for nothing exotic, only that you use a machine without hesitation: find files by size, build a frequency report, create links, fix permissions, separate outputs.

The L2 test is launched here, because this is the page where you come to measure where you stand. A fresh VM, a complete mission, nine deliverables, and no dictated command. The last test reboots the machine before looking a second time: whatever does not survive the reboot scores zero.

How do the RHCSA and LFCS mock exams work?

Both mock exams reproduce the format of the certifications: practical tasks scored on the state of the machine, a threshold of 70 points out of 100, and no hints. Prepare the context with the RHCSA hub or the LFCS hub, then start the exam.

The RHCSA mock exam reproduces the conditions of the EX200 with 20 tasks spread over 2 VMs, a server and a client, for a duration of 180 minutes. It covers storage, networking, users, services, SELinux, packages and boot recovery.

Terminal window
dsoxlab run rhcsa-mock-exam

The LFCS mock exam covers the 5 official domains in 17 tasks on one Ubuntu 24.04 VM, each task tied to an objective published in the syllabus.

Terminal window
dsoxlab run lfcs-mock-exam

What does the production capstone test, and why does the machine reboot?

A learner who takes no certification deserves a final test too. capstone-mise-en-production provides it: a fresh VM, an application delivered in /opt/livraison, and a mission, to put it into service.

Terminal window
dsoxlab run capstone-mise-en-production

Nine deliverables are scored: storage on a logical volume mounted through fstab, a service account without a shell, a service that is active and enabled, SELinux enforcing with a labelled port and a durable context, a firewall opened permanently, a page fetched from the client, a persistent journal, sshd without password or root login, and a scheduled backup that has already produced an archive.

The tenth test really reboots the machine, then asks for the page again. It is not a formality: the four ways of delivering a server that works on acceptance day and not the day after only show up at reboot. A mount missing from fstab, a service never set to enabled, a firewall rule added without --permanent, an SELinux label set with chcon instead of semanage. If the page comes back, all four are right.

What does the troubleshooting capstone test, when the symptom says nothing?

The two mock exams assess a certification. The capstone-serveur-casse capstone assesses something else, troubleshooting, and it fills a gap: every fault lab in the section announces its domain in its title. "Fix an SELinux problem" has already given away half the diagnosis.

Here, you receive only a symptom, "the internal site no longer answers". The lab built a working site, proved it, then broke one single thing drawn at random among six, without naming it: service stopped, wrong port, firewall closed again, SELinux context, docroot permissions, listening limited to the loopback.

Terminal window
dsoxlab run capstone-serveur-casse

The verdict is taken from the client, on a second VM: a curl localhost can answer 200 while nobody can reach the service. And 3 of the 7 tests are safeguards: switching SELinux to permissive, stopping the firewall or opening the docroot to everyone makes the site answer and costs 35 of the 100 points. A server that answers because it is no longer protected is not repaired.

How do I install the catalogue and follow my progress?

The linux-dsoxlab-training repository gathers all the labs, their environments and the scoring engine. The dsoxlab CLI drives the full cycle: list the labs, start an environment, validate your work and follow your progress by level.

What does the lab catalogue contain, level by level?

The table gives the map of the catalogue: how many labs each level holds and what they cover. Each lab is called from the lesson that teaches it, with its exact identifier to pass to dsoxlab run: that is the best place to start it, right after reading the guide.

LevelLabsWhat they cover
l120Terminal, help, tree, paths, links, search, text, redirections, archives, permissions, first script
l218Users, sudo, ACLs, passwords, packages and repositories, partitions, filesystems, LVM, RAID, LUKS, swap, NFS, autofs
l314Boot and targets, GRUB, sysctl, tuned, services and units, journald, processes, cron, at, timers, lost SSH access
l415Static networking, bonding, NAT, NTP, firewall, SELinux, SSH hardening, LDAP, reverse proxy, Podman
lfcs6Debian and Ubuntu specifics: APT, netplan, ufw, AppArmor, quotas, CIFS
Drills9One domain per drill, timed, no hints
Capstones4Production, troubleshooting, RHCSA and LFCS mock exams

Key takeaways

  • Validation climbs four steps: lab, drill, capstone, mock exam.
  • Every test is scored on the state of the machine, never on the commands typed.
  • Each level ends with a test: drill-essential-commands (L1), capstone-mise-en-production (L2), capstone-serveur-casse (L3).
  • The L2 capstone reboots the machine before the final check: what does not persist scores zero.
  • The mock exams pass at 70 points out of 100, with no hints.
  • Each lab is launched from the lesson that teaches it, with dsoxlab run <id>.