RHCSA Exam Prep 2026: 30-Day Study Plan with Labs

Quick summary: RHCSA in 2026 (EX200V9, based on RHEL 9) is a three-hour, fully hands-on exam covering everything from basic shell tasks to SELinux, container management with podman, and tuned profile selection. This plan gives you 30 days of focused study, daily practice tasks, mock exams, and the exact time allocation strategy that has worked for hundreds of candidates we have coached. No fluff — just what you need to do every day for a month to walk in confident on test day.

RHCSA exam prep 2026 30-day study plan with practice labs

What the RHCSA Exam Actually Tests in 2026

RHCSA is performance-based — you sit at a real RHEL 9 system (or two), get a list of tasks, and have 180 minutes to complete them. There is no multiple choice. There is no partial credit for "almost." Either the task is configured correctly and survives a reboot, or you get zero points for it.

The current objectives, based on the published RHCSA EX200V9 exam, cover:

Tools: bash, vim/nano, ssh, terminal navigation, file management, archiving
Boot, reboot, recovery: changing runlevels (targets), recovering root password, troubleshooting boot issues
Storage: partitioning with parted/fdisk, LVM, swap, encrypted volumes (LUKS), persistent mounts
Filesystems: creating ext4/xfs filesystems, finding files, ACLs, autofs
System operation: scheduling tasks (cron, systemd timers), managing services, journal logs, tuned profiles
Networking: configuring static IPs with nmcli, hostname, /etc/hosts, firewalld basics
Users and groups: creating, modifying, password aging, sudo configuration
Security: SELinux booleans and contexts, file permissions, basic firewalld zones, SSH key auth
Software: dnf repositories, package install/update, modular streams
Containers: managing rootless containers with podman, container images, persistent storage, systemd integration

The 2026 version puts noticeably more weight on container operations than older versions — expect at least 15-20% of your time on podman tasks.

Setting Up a Realistic Practice Environment

Reading about Linux does not pass the RHCSA. Doing Linux does. You need a practice environment that matches the exam.

Option 1: AlmaLinux or Rocky Linux 9 in VMs

Free, identical to RHEL 9 from the exam's perspective. Set up two VMs (call them rhcsa-1 and rhcsa-2) on KVM, VirtualBox, or VMware Workstation. Give each 2 vCPU, 2 GB RAM, and a 20 GB disk plus a second 5 GB disk for storage exercises. The second VM is essential for SSH key exchange, autofs, and remote mount tasks.

Option 2: Red Hat Developer Subscription

Free for personal use; gives you access to actual RHEL 9 ISOs and the Red Hat documentation portal. The exam runs on RHEL, so practicing on RHEL is the closest match.

Option 3: Cloud-based labs

Several training providers offer RHCSA practice environments. Useful as a supplement; not a substitute for owning a local lab you can break and rebuild without a credit card.

The 30-Day Plan: Week-by-Week Breakdown

Week 1: Foundations and Daily Tools (Days 1-7)

The goal this week is fluency with the basic operations. You should be able to do these in your sleep:

Day 1 — Install RHEL/AlmaLinux 9 from scratch, set hostname, configure static IP with nmcli, set up SSH key authentication.
Day 2 — Practice all common file operations: find, grep, tar, gzip, xz, regex basics, redirection, pipes.
Day 3 — vim drill: search/replace, navigation, multi-file editing, recovering from common mistakes. You will edit dozens of config files in the exam.
Day 4 — User and group management: useradd, usermod, passwd, chage, primary vs secondary groups.
Day 5 — File permissions deep dive: chmod symbolic and numeric, setuid/setgid/sticky, default ACLs.
Day 6 — Sudo configuration: per-user, per-group, passwordless, restricted commands. Practice with visudo.
Day 7 — Mock exam #1: 90 minutes, focus on Week 1 topics. Score yourself honestly.

Week 2: Storage, Filesystems, and Boot (Days 8-14)

This week is the largest single category by exam weight, and the highest-risk area for losing points to silly mistakes (forgetting to make mounts persistent in /etc/fstab, mistyping a UUID).

Day 8 — Partitioning with parted: GPT vs MBR, creating partitions, aligning to sector boundaries.
Day 9 — LVM end-to-end: pvcreate, vgcreate, lvcreate, extending and shrinking, snapshots.
Day 10 — Filesystems: mkfs.xfs, mkfs.ext4, resizing, mounting, /etc/fstab with UUIDs and labels.
Day 11 — Swap and tmpfs: creating swap files and partitions, tmpfs mounts.
Day 12 — LUKS encryption: creating an encrypted volume, mounting at boot via /etc/crypttab.
Day 13 — Boot recovery: rescue mode, single-user mode, resetting the root password, troubleshooting boot failures.
Day 14 — Mock exam #2: 120 minutes, weighted toward storage. Diagnose what cost you points.

Week 3: Services, Networking, Security (Days 15-21)

Day 15 — systemd: enabling, disabling, masking, isolating targets, default target. Read at least three real unit files in /usr/lib/systemd/system/.
Day 16 — systemd timers vs cron: writing a timer, troubleshooting why it did not fire.
Day 17 — Networking: nmcli connection management, bonds, teams, bridges, hostname, DNS configuration.
Day 18 — firewalld: zones, services, ports, rich rules, persistent vs runtime config.
Day 19 — SELinux: getenforce, enforce/permissive/disabled, booleans, file contexts, semanage, restorecon. This is where many candidates lose points.
Day 20 — dnf: enabling repositories, GPG keys, modular streams, version locking.
Day 21 — Mock exam #3: full 180 minutes. The first time you do the real time pressure.

Week 4: Containers, Practice, Polish (Days 22-30)

Day 22 — podman basics: pulling images, running containers, port mapping, volumes.
Day 23 — Rootless podman: setting it up, common pitfalls, persistent storage as a non-root user.
Day 24 — Container as a service: generating systemd units with podman generate systemd, enabling on boot.
Day 25 — Targeted practice on your weakest topic from mock exams 1-3. Be honest about what you are bad at.
Day 26 — Mock exam #4: full 180 minutes. Different scenarios than mocks 1-3.
Day 27 — Review every task category one more time. Focus on the things you have to look up.
Day 28 — Mock exam #5: full 180 minutes. Aim for under 150 minutes (leave a buffer for the real thing).
Day 29 — Light review only. Do not cram. Make sure your test setup is documented (where, when, what to bring).
Day 30 — Rest. Sleep well. Eat normally. Do not study the morning of the exam.

The Time-Management Strategy That Wins

180 minutes feels like a lot until the clock is ticking. The strategy that consistently produces passing scores:

First 10 minutes — read everything, prioritize. Skim every task. Note ones that are quick (5 minutes) and ones that look hard (15+ minutes). Do not start working yet.
Next 30 minutes — knock out the easy stuff. Hostname, basic file permissions, user creation, simple firewall rule, SELinux boolean. Bank points fast.
Next 90 minutes — work the medium tasks. Storage configuration, services, networking, podman tasks. These are most of the exam by weight.
Last 30 minutes — hardest tasks and verification. Tackle the things you put off, then VERIFY EVERY TASK survives a reboot. Reboot the VM. Re-verify each task. This is where many candidates lose easy points.
Last 10 minutes — buffer. One last verification pass. Make sure SELinux is in the requested state. Make sure all services are enabled, not just running.

The Top Five Things Candidates Forget

Persistent mounts in /etc/fstab. The mount works now but disappears after reboot — zero points.
systemctl enable in addition to start. Service runs but does not survive reboot — zero points.
SELinux contexts on relocated files. Web server fails to serve a file because the context is wrong; httpd_sys_content_t is your friend.
firewalld --permanent. Without it, the rule disappears after reload.
Setting the default target with systemctl set-default. Booting into multi-user.target by default if asked, not graphical.

Resources Worth Using

Red Hat's official RHCSA exam objectives — read every line, twice. Anything not listed is out of scope.
The actual man pages — you have them in the exam. Practice reading them under time pressure. man -k partition, man 5 fstab, man systemd.timer.
Sander van Vugt's RHCSA video courses — widely considered the best paid resource for current EX200V9.
Asghar Ghori's "RHCSA & RHCE 9" book — comprehensive, recently updated for the V9 objectives.
Free practice question banks — search GitHub for "RHCSA practice"; several open repositories have lab scenarios.

What to Do on Exam Day

Eat breakfast. Three hours of intense concentration on an empty stomach is a mistake.
Show up early. Whether the exam is at a Pearson VUE center or remote-proctored, technical setup eats time.
Bring (or have ready) your photo ID. You will be turned away without it.
For remote exams: tidy your workspace. Proctors will ask you to show the room; clutter delays the start.
Use the man pages. No bonus points for memorization; you have the docs.

Common Mistakes Candidates Make on Exam Day

After coaching dozens of candidates through RHCSA, the patterns of failure are remarkably consistent. Avoiding these specific mistakes is worth more than another week of generic study.

Skipping the read-through. Candidates dive into task one and grind through sequentially. Halfway through they hit a hard task, lose 30 minutes on it, and run out of time before reaching the easy tasks at the end. Always read every task before starting any of them, mentally tag each as easy/medium/hard, and work easy-to-hard regardless of the printed order.

Not rebooting before submitting. The exam scoring boots a fresh instance of your machine and runs automated checks. If your service is started but not enabled, your mount works but is not in /etc/fstab, your SELinux context is set with chcon (transient) instead of semanage (permanent) — you get zero on those tasks. Reboot at the 150-minute mark and verify everything still works.

Treating man pages as a last resort. The exam includes the full man pages and Red Hat documentation locally. Use them confidently. man -k partition finds every relevant page; man systemd.timer shows the exact OnCalendar syntax. Time spent looking up the right syntax is faster than time spent fixing wrong syntax.

Ignoring the small tasks. A candidate spent 45 minutes troubleshooting an LVM extension that turned out to be a physical-volume confusion, while skipping a simple "create a user with these properties" task that would have taken 90 seconds. Each task is worth points; do not let one stuck task starve the others.

Forgetting to save the root password reset. The single most-tested boot-recovery task is "reset the root password." Candidates do it, log in successfully, then forget to verify SELinux relabeling completed (autorelabel) before moving on. The relabel happens on next boot and can take time; account for it when planning.

Configuring firewalld with --runtime instead of --permanent. The runtime config disappears at firewalld reload or reboot. Always use --permanent for any rule that should survive, then firewall-cmd --reload to make it active. This is one of the highest-frequency single-point losses on the exam.

Burning time on perfect formatting. The exam grader does not care if your /etc/fstab has perfectly aligned columns or if your sudo rules are commented. It cares whether the configuration achieves the stated outcome. Functional first, beautiful second — and only if you have time at the end, which you usually will not. Get the task working, run the verification, move on to the next task. Polish is the enemy of points on a timed practical exam.

Frequently Asked Questions

What is the passing score?

210 out of 300 (70%). You will know your result within 3 business days, not at the end of the exam.

Can I skip questions and come back?

Yes. The exam is one big task list, not a sequential test. Work in the order that maximizes your score.

Is RHCSA worth it in 2026?

Yes for entry-level Linux admin / DevOps roles, especially in enterprises that use RHEL or its derivatives. The hands-on format is what employers value — it proves you can do the work, not just describe it.

How long is RHCSA valid?

Three years. You can recertify by passing RHCSA again, by passing a higher-level Red Hat exam (RHCE, RHCA), or by participating in the Red Hat Skills Path program.

Should I take RHCE next?

If you work with Ansible at scale, yes. RHCE is now Ansible-focused (not the broad system admin focus of older RHCE). If you do not work with Ansible, look at security, OpenShift, or specialty Red Hat certifications instead.

The Bottom Line

RHCSA is not a hard exam if you actually practice. It is a brutal exam if you only read about Linux. Spend the 30 days doing the work in a real lab, take five honest mock exams, and walk in knowing your time-management plan. The candidates who fail are almost always the ones who skipped the hands-on practice; the ones who pass are the ones who broke and rebuilt their lab VMs a hundred times.

Categories

RHCSA Exam Prep 2026: 30-Day Study Plan with Hands-On Practice Labs

What the RHCSA Exam Actually Tests in 2026

Setting Up a Realistic Practice Environment