Linux · 10 min read

What is RHCSA and how does the EX200 exam work?

RHCSA (Red Hat Certified System Administrator) is Red Hat's official entry-level certification in Linux system administration, and the exam code is EX200. There are no tests or multiple-choice questions: the candidate carries out tasks in a real RHEL environment, and the result is graded by the final actual state of the system. In other words, what is tested is not memorized answers but the ability to work in the terminal.

What is RHCSA and who is it for?

RHCSA is an official certification that confirms the ability to manage a Red Hat Enterprise Linux (RHEL) system day to day. The exam code is EX200, and it is considered the first step on Red Hat's certification path. The certification means that you can install a server, manage users, extend a disk, start a service and configure security settings correctly.

This certification is intended not for one specific role but as a common foundation for several career directions. Without knowing Linux, it is impossible to go deep in any branch of modern infrastructure.

• System administrators — day-to-day management and support of RHEL servers.
• NOC (network operations center) and infrastructure teams — monitoring, log analysis, service recovery.
• Those moving into DevOps / DevSecOps — containers, systemd and package management are built on this foundation.
• Candidates for the cybersecurity defense team (Blue Team) — to understand an attack, you first need to understand the system itself.
• Beginners — RHCSA is an entry-level certification and does not require any formal prerequisite.

How does the RHCSA exam work — what is its format?

EX200 is an entirely practical exam. What opens in front of you is not a question sheet but a running RHEL machine, along with a list of tasks to complete. What is graded is not how you solved a task but the state of the system at the end of the exam.

This is the most important detail of the format: typing the command correctly is not enough — the result must survive a reboot as well. Grading is automatic and checks the real configuration of the system. The exam is offered in two ways — a remotely proctored exam (Remote Exam) and an exam at an accredited test center.

What topics are tested in the exam?

The official exam syllabus is divided into several sections. The table below lists these blocks in English, together with the tools used in each block.

The exam syllabus is updated from time to time by Red Hat. Before starting preparation, it makes sense to read the official list of exam objectives once and align your own lab plan with it.

What is the difference between RHCSA, RHCE and other Linux certifications?

The main difference is the format. Many Linux certifications are assessed with a multiple-choice test — there, theoretical knowledge is measured. In Red Hat exams, however, the system either works or it does not; there is no partial answer. For this reason, preparation is done not by reading books but by building things in the lab over and over again.

How much time is needed to prepare for RHCSA?

In the experience of our own program, a realistic timeframe for a participant starting from scratch is about 4 months, assuming 8–10 hours a week of theory classes and lab work. A person with Linux experience can shorten this period, but hours at the keyboard are still needed to build practical habits.

1. Month 1 — the terminal, the file hierarchy, Vim, text processing, user and group management, permissions and ACLs.
2. Month 2 — disk partitioning, XFS/ext4, extending LVM, swap, networking with nmcli, processes, systemd and cron.
3. Month 3 — DNF/RPM and repositories, SELinux contexts, firewalld, key-based SSH authentication, journalctl, Chrony, GRUB2 and root password recovery.
4. Month 4 — containers with Podman, running a container as a systemd service, Apache HTTPD, NFS and AutoFS, then full exam simulations.

Where do candidates get stuck most often on the RHCSA exam?

Most of the points lost in the exam come not from a lack of knowledge but from carelessness. The following are the most frequently repeated mistakes.

• Not making the configuration persistent — the service is started but `systemctl enable` is not run, and it stays down after a reboot.
• Writing a firewalld rule without `--permanent` and not running `--reload` — the rule is lost after a reboot.
• Forgetting the SELinux context — the file is in the right place and the permissions are correct, but Apache HTTPD does not serve the page.
• A typo in /etc/fstab — at the next boot the system drops into emergency mode, and all tasks are put at risk.
• Extending the volume without growing the file system — `lvextend` is run, and `xfs_growfs` is forgotten.
• Time management — spending half an hour on one hard task and leaving the easy tasks blank.
• Configuring the network out of GUI habit — a configuration not written with `nmcli` may not show up during grading.

All of these mistakes have one common solution: check the result after every task. Commands such as `systemctl is-enabled`, `firewall-cmd --list-all`, `ls -Z` and `mount -a` take a few seconds but save the points for a task.

# A typical set for verifying that a change is persistent
systemctl is-enabled httpd && systemctl is-active httpd
firewall-cmd --permanent --add-service=http && firewall-cmd --reload
mount -a && df -h /data
ls -Z /var/www/html/index.html

What lab environment should you build for preparation?

It is not possible to prepare by reading alone. Building your own virtual lab is the work of the first week.

1. Choose a distribution: Red Hat Enterprise Linux (through the developer program), or the compatible AlmaLinux / Rocky Linux.
2. Install a hypervisor: KVM on Linux, VirtualBox or VMware on Windows or macOS.
3. Create at least two virtual machines — a second machine is required for the SSH, NFS and AutoFS tasks.
4. Attach an empty disk to each machine: the LVM, swap and /etc/fstab exercises do not work without it.
5. Take a snapshot immediately after a clean installation — if you make a mistake, you will be back in 5 minutes.
6. Repeat each topic from scratch at least twice: the first time with notes, the second time with only the man pages.

• Memory: 2 GB of RAM per virtual machine is usually enough, and if you do not install a graphical interface, even less works.
• Do not install a graphical interface — in the exam, too, the work is done in the terminal.
• Disconnect the internet and practice working with a local repository.
• Name snapshots by topic: `temiz-sistem`, `lvm-oncesi`, `selinux-lab`.

What strategy works on exam day?

1. First read all the tasks from beginning to end; mark the easy and familiar ones.
2. Finish the easy ones first — tasks carry equal points, and a hard task does not give more points.
3. Group interdependent tasks: for example, do the disk storage tasks one after another.
4. Verify after every change: for a service, `systemctl enable --now`, then `is-enabled` and `is-active`.
5. When you forget something, use the man pages — `man -k` and `man 5 fstab` are available in the exam.
6. Do not get stuck on one task for more than 15 minutes; mark it and leave it for later.
7. When 20–25 minutes remain, reboot the system and check all the results one by one.
8. After the reboot, confirm the mount points, services, networking and firewall rules.

What does RHCSA offer for a career in Azerbaijan?

In the server infrastructure of banks, telecom companies, government bodies and large corporate companies in Azerbaijan, the RHEL family (RHEL, AlmaLinux, Rocky Linux) is a commonly encountered choice; there are no open statistics on the exact market share. For an employer, RHCSA is a concrete and verifiable signal: the candidate can finish a task on a real system.

The certification itself is not a guarantee of a job. However, it increases the chance of reaching the technical stage of an interview and turns the phrase «I know Linux» on a CV into a measurable fact.

• System administrator and server support — a directly matching role.
• NOC and infrastructure engineering — monitoring, log analysis, fault recovery.
• DevSecOps — Linux is a basic requirement for containers, CI/CD and automation.
• Defense team (Blue Team) — the ability to look for traces on a server during incident response.
• Next step — RHCE (automation with Ansible) or the cloud track.