EX200: Demonstrate Real Red Hat Linux Administration

Red Hat's EX200 is a performance-based examination for the Red Hat Certified System Administrator (RHCSA) credential. Unlike a knowledge test that merely asks which command looks familiar, EX200 requires a candidate to configure and troubleshoot a working Red Hat Enterprise Linux environment. The vendor's current exam page identifies Red Hat Enterprise Linux 10 as the underlying release and includes shell tools, software, scripting, services, storage, filesystems, networking, users, and security. Configuration changes must persist after reboot without manual intervention. That persistence requirement changes how a competent candidate approaches nearly every lab task.

The current Red Hat certifications also describes RHCSA as a foundation for higher-level enterprise Linux and Ansible engineering paths. But EX200 is valuable on its own: successful administrators can identify system state, make controlled changes, verify outcomes, and recover when a configuration fails. A long command list is not enough. During the practical exam, internet access is unavailable and candidates cannot use personal notes or books; publisher rules describe what documentation supplied with the system may be used. Check the live candidate page for allowed tools and the exact environment before registering.

Know the shell, files, and permissions under pressure

Core shell competence includes reading and editing text, searching files, redirecting output, building pipelines, using archives, and navigating documentation. Operators such as >, >>, |, and 2> have distinct meanings. Confusing standard error with standard output can hide a failure or overwrite a record. Test pipelines on small inputs and inspect exit codes where needed. Commands should be chosen for predictable behavior, especially when modifying paths containing spaces or potentially ambiguous patterns.

File permissions require understanding the owner, group, and other access bits, as well as the difference between permissions on a file and permission to traverse its parent directory. A user with read permission on a file may still be blocked by an inaccessible directory. Hard links and symbolic links also behave differently when targets move or are removed. The subject of hard links and soft links in Linux is worth studying in the context of inodes, directory entries, and application access rather than treating the two names as interchangeable.

Text-editing skill matters because many recovery tasks require correcting a configuration file. Use approved tools confidently, validate syntax when a service provides a validator, and maintain backups or checkpoints where appropriate. The ability to edit a file is not the same as knowing whether the edited configuration will be read on service restart. Check the location, active unit, inclusion rules, and logs before assuming a change took effect. Reading built-in man documentation can be a faster and safer strategy than relying on a half-remembered flag.

Manage users, privilege, and authentication boundaries

System administrators create and modify accounts, groups, passwords, password aging, and privilege assignments. A user's primary group and supplementary groups can influence access decisions. Inspect effective memberships and process context after making changes. If a service account cannot read a directory, the cause might be conventional Unix permissions, an access control list, SELinux labeling, or a mount issue. Repeatedly granting broad access without identifying the cause weakens security and may not solve the problem.

Administrative privilege should be granted deliberately. sudo can authorize controlled commands; switching directly to a privileged account carries different accountability considerations. Using sudo and su safely is relevant to learning how to confirm who is executing a command and avoid accidentally modifying the wrong environment. The correct response to a permission error is usually to investigate the relevant policy, not immediately disable controls or apply world-writable permissions.

SSH configuration involves service availability, permitted authentication methods, key handling, and host trust. Test access from the intended client after changing settings, particularly when disabling a login path. Preserve a recovery route when operating remotely. If an administrator locks out all management access through a network or authentication change, knowing the theoretical correct setting is of little use unless a console or other recovery method remains available.

Operate services, boot targets, and logs

The systemd service manager provides a framework for managing services and boot targets. Candidates should know how to inspect a unit's state, start or stop a service, enable it for future boots, and investigate why it failed. systemctl start and systemctl enable solve different requirements: one changes the current state, the other establishes boot-time behavior. A successfully started service can still be unusable because it cannot bind a port, open a file, or communicate with a dependency. Logs and service status must be interpreted together.

The system journal offers a chronological view of many events. Learn to filter by unit, time range, priority, or boot. Persistent journal configuration can be important when debugging failures that occurred before a restart. A log entry describing denial can point toward SELinux or ordinary permissions; a connection refusal can indicate a stopped service or the wrong listener. Collect sufficient evidence before attempting multiple unrelated configuration changes, or it becomes difficult to know which action fixed the issue.

Boot and recovery skills matter. Understand targets, bootloader configuration, and how to recover from a broken configuration without making permanent security exceptions. Linux boot commands and system startup support study of state transitions and diagnostics. Lab exercises should include a change that appears successful but disappears after reboot; identifying that persistence failure is a central EX200 habit.

Build reliable storage and filesystem configurations

Local storage objectives include GPT partitions, physical volumes, volume groups, logical volumes, filesystems, swap, and permanent mounts. A logical volume can grow independently of the filesystem layered on top of it; expanding one does not automatically mean the other has usable additional space. Before resizing, inspect block devices, free extents, filesystem type, mounted state, and available backup or snapshot protection. Commands that modify partition tables or filesystems can be destructive if a device name is mistaken, so verify identifiers carefully.

Mounting by universally unique identifier (UUID) or label helps avoid unstable device-name assumptions. The /etc/fstab configuration must be syntactically correct and supported by actual device and filesystem state. A configuration that works only until the next reboot fails the administrator's obligation. Test mounting and inspect diagnostics before concluding that the system is ready. Network storage with NFS or automounting introduces dependencies on name resolution, network access, export permissions, and service availability.

Permissions interact with filesystems and access control lists. A mounted volume can appear inaccessible because of mode bits, mount options, network identity mapping, or SELinux context. Approach problems in layers. Check the correct path and mounted filesystem, then examine access policy, ownership, logs, and the service identity. This structured sequence is safer than recursively changing ownership over an unknown mount point.

Configure networking and security controls together

Static addressing, hostnames, name resolution, and network service persistence must be verified using the supported management tools of the target RHEL release. It is easy to configure an IP address that works for a few minutes while failing to establish a persistent connection profile. Confirm the active route and resolver behavior after changes. A server can reach a gateway yet fail an application because DNS resolution or a remote policy is wrong. The Linux traceroute command can help with conceptual path troubleshooting, though the exact exam tasks must come from Red Hat's stated objectives.

Firewalld zones, services, and ports control traffic exposure. Understand the difference between a runtime change and a permanent configuration. If a web service is reachable locally but unavailable remotely, inspect its listener, firewall policy, routing, and host access rather than opening unrelated ports. Administrative changes should be narrow enough to meet the requirement without expanding attack surface. Test the real connectivity path and confirm the rule survives the necessary lifecycle events.

SELinux is a critical part of Red Hat administration. Enforcement modes, file contexts, port labels, and policy Booleans can influence service behavior. Setting SELinux to permissive may help distinguish a policy denial during diagnosis, but leaving it disabled is not a professional solution to a mislabeling problem. Use appropriate inspection and context restoration methods, then verify the service under the intended enforcing policy. Know how standard Unix permissions and SELinux decisions combine, since granting access in one layer does not override a denial in the other.

Install software and automate small tasks reliably

RPM repository configuration and package management require understanding trusted sources and package dependencies. The RHEL 10 EX200 objectives also include configuring and handling Flatpak repositories and packages, reflecting an edition-specific detail that older course notes may omit. Confirm which software sources are actually available in the exam environment. Installing a package is not proof the associated service is configured, enabled, and working as requested.

The official objectives include simple shell scripts with conditionals, loops, positional arguments, and command output. An administrator should be able to write a script that checks for a required file, creates a directory only if absent, logs a status, or processes names safely. Scripts need meaningful exit status and predictable quoting. Test them on cases such as missing arguments, empty output, or unavailable services. Linux learning resources can support basic command practice, but hands-on RHEL 10 objectives remain the controlling study list.

Time-based tasks may use cron, at, or systemd timers depending on the specified requirement. Understand what executes under which identity and environment, and how to verify that a scheduled task ran. A task that executes interactively but fails under a minimal scheduled environment may be missing PATH assumptions or access rights. Treat logging and alerting as part of the outcome rather than as optional decorations.

Prepare in a repeatable lab, not by memorizing screenshots

Use a supported Red Hat Enterprise Linux lab to create accounts, alter permissions, configure services, build storage, implement a firewall rule, restore SELinux context, and schedule a task. After each operation, verify actual behavior and reboot where persistence matters. Intentionally break one dependency and diagnose it from logs and system state. Practice from a clean starting snapshot so that success does not depend on accidental leftovers from a previous attempt.

The official objectives are the best checklist. A candidate should be able to complete each relevant task without external help and explain the verification method. Build a compact command reference through practice, but remember that examination rules do not permit bringing a private reference into the session. The goal is fluency under real constraints. If a topic such as text editing with nano improves the ability to correct configuration safely, connect it to that actual workflow rather than treating editor choice as an exam shortcut.

RHCSA performance reflects operational discipline: inspect before changing, preserve least privilege, test the result, and ensure settings remain correct after reboot. That discipline is more valuable than fast typing and is what makes EX200 preparation applicable to production administration.