RHCSA Exam Essential Commands and System Review

Updated 9 November 2026 · Standard formula, shown below

The RHCSA exam assesses practical Linux administration, so reviewing essential commands means learning to use them to inspect, configure, and troubleshoot a system—not just memorizing a list. Focus on navigating files, managing users and permissions, controlling services, handling storage and networking, and verifying changes from the command line.

What the RHCSA Exam Tests

RHCSA is the Red Hat Certified System Administrator certification. Its exam is performance-based: candidates complete administrative tasks on a live system rather than answering only multiple-choice questions. The objectives can change over time, so use the current official exam objectives as your checklist and treat command examples as practice, not as a substitute for that document.

Because tasks are practical, it is not enough to know that a command exists. You should be able to choose suitable options, make a persistent configuration when required, and confirm that the requested outcome survives a reboot or applies to the intended user and service. The exam environment may not provide the same convenience as a personal workstation, so practice from a terminal and learn to read local manual pages.

File, Directory, and Text Commands

File operations are foundational because many other administration tasks involve editing configuration files, locating logs, or setting ownership. Be comfortable with these commands and their consequences:

pwd, ls -la, and cd show where you are and help inspect directory contents, including hidden files.
cp, mv, and rm copy, move or rename, and remove files. Check paths carefully before destructive operations.
mkdir -p creates a directory path, including missing parent directories; touch creates an empty file or updates its timestamp.
cat, less, and head/tail display file contents. tail -f is useful for watching a log as it changes.
grep, find, and locate help search. find searches the filesystem directly; locate relies on an index that may not reflect recent changes.

Also practice shell redirection and pipelines: > replaces a file’s contents, >> appends, and | sends one command’s output to another. For example, grep -i error /var/log/messages | tail filters matching lines and displays the latest ones. Know that sudo or a root shell may be needed for protected files, and avoid confusing a command’s output with a successful configuration change.

Users, Groups, Permissions, and Processes

Account administration requires knowing how identity, group membership, and file access fit together. Review useradd, usermod, userdel, groupadd, and passwd. Use id and getent passwd USER to inspect account information, and check group membership with groups USER or id USER.

For file access, practice chmod for permission bits and chown for ownership. A command such as chmod 640 report.txt gives the owner read/write access, the group read access, and others no access. Learn symbolic modes too, such as chmod u+x script.sh. The umask affects default permissions on newly created files; it does not normally change permissions on existing files. If access still fails, inspect every directory in the path and distinguish ordinary permissions from access-control lists, which can be viewed with getfacl.

For processes, ps, top, and pgrep help identify what is running. kill sends a signal to a process; use the least forceful option that solves the problem rather than defaulting to an immediate kill. Use jobs, bg, and fg to manage jobs started in the current shell.

Services, Logs, and Software

On modern Red Hat Enterprise Linux systems, systemd manages services. Practice systemctl status SERVICE, systemctl start SERVICE, systemctl stop SERVICE, and systemctl restart SERVICE. Starting a service now is different from enabling it to start at boot: use systemctl enable SERVICE for boot-time activation, or systemctl enable --now SERVICE when both are needed.

When a service does not work, inspect its status and recent journal entries rather than repeatedly restarting it. journalctl -u SERVICE filters the system journal by unit; journalctl -b shows entries from the current boot. Also check configuration syntax, file permissions, port conflicts, and whether the service is enabled. A service can be active while still failing to meet the task—for example, it may be listening on the wrong address.

For package management, know the system’s available tools and the exam objectives. Red Hat-family systems use RPM packages and DNF-based workflows; commands such as dnf install, dnf remove, and rpm -q cover common installation and query tasks. Package availability may depend on configured repositories, so distinguish a missing package from a repository or network problem.

Storage, Networking, and System Inspection

Storage tasks often combine inspection, partitioning, filesystems, mounts, and persistent configuration. Start with lsblk, blkid, df -h, and du -sh to understand devices and usage. Tools such as fdisk or parted alter partition tables, while mkfs creates a filesystem and is destructive to existing data on the target. Verify the device name before running either operation.

To mount a filesystem temporarily, use mount; to make a mount persist across boots, configure /etc/fstab appropriately. Test changes with mount -a before rebooting, and use a filesystem UUID where suitable rather than relying only on device names that can vary. For logical volumes, review the roles of pvcreate, vgcreate, and lvcreate, along with filesystem creation and mounting.

For networking, know how to inspect interfaces and addresses with ip addr, routes with ip route, and name resolution with tools such as getent hosts. ping can test basic reachability, but a failed ping alone does not prove a host is unavailable; filtering or routing may block it. Learn how NetworkManager connections are inspected and managed with nmcli, and verify both the active configuration and persistence after a reboot when required.

A Practical Review Method

Build practice sessions around outcomes instead of isolated flash cards. For each objective, perform the task on a virtual machine, then verify it using a second command or a fresh login. A useful cycle is:

Read the task and identify the target, required state, and whether it must persist.
Inspect the current system before changing anything: check files, services, devices, or network settings.
Make the smallest appropriate change, paying attention to exact paths, names, and permissions.
Verify the result with commands such as systemctl status, id, findmnt, or ip addr.
Reboot or reconnect when persistence is part of the requirement, then verify again.

Practice recovery as well as setup. Deliberately make a harmless configuration mistake in a disposable lab, locate the relevant log or status output, and correct it. This develops the habit of troubleshooting from evidence rather than guessing. Keep a compact study checklist, but avoid relying on notes that do not explain why a command is appropriate.

Frequently Asked Questions

Is the RHCSA exam mostly command memorization?
No. Command familiarity matters, but the exam emphasizes completing administrative tasks. You need to understand the required system state, choose commands that achieve it, and verify the result.

Which commands should I study first?
Start with filesystem navigation and editing, users and permissions, systemctl and journalctl, package management, storage inspection, and network inspection. Then follow the current exam objectives to identify remaining topics.

Do I need to memorize every command option?
Prioritize commonly used options and the ability to consult man pages and command help. The goal is to work accurately under exam conditions, not to memorize every option for every utility.

Why is a service running but not working?
“Active” only reports a service state. Check its logs, configuration, listening address or port, dependencies, permissions, and whether it is enabled at boot if persistence is required.

What is the safest way to practice storage commands?
Use a disposable virtual machine with virtual disks, confirm device names with lsblk, and understand that partitioning and formatting can erase data. Do not experiment on a disk containing files you need.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.