Red Hat Certified Engineer (RHCE) #1: Exam Overview — the environment, time management, ansible-navigator vs ansible-playbook

If the 16-post RHCSA series had you learning how to carry out RHEL system administration tasks by hand, the next step is automating those tasks with Ansible. In the Red Hat certification hierarchy, the upper-tier hands-on exam that sits on top of RHCSA is the Red Hat Certified Engineer (RHCE, exam code EX294). This series is a track that unpacks every domain you need to pass RHCE across 19 posts.

RHCE is no longer an exam where you type commands by hand — it’s an exam where you configure systems declaratively with Ansible playbooks. The user creation, LVM, firewalld, and SELinux work you did by hand in RHCSA, you now automate with idempotent playbooks. So this first post locks in not just the exam structure but also the Ansible execution environment and a strategy for running your 4 hours.

What kind of certification is RHCE #

RHCE validates, hands-on, your ability to automatically configure RHEL systems with Ansible. Where RHCSA was the job of managing a single system by hand, RHCE configures multiple systems consistently from a single playbook. You complete tasks like these within the time limit.

• Configure inventory and ansible.cfg and connect to multiple hosts
• Manage packages, services, and files with idempotent playbooks
• Dynamically generate per-host configuration with variables, facts, and Jinja2 templates
• Handle errors with block/rescue and encrypt secrets with Vault
• Modularize configuration with roles, collections, and rhel-system-roles
• Automate RHCSA’s manual work (users, LVM, firewalld, SELinux) with playbooks

Someone who passes this exam moves beyond being an administrator who manages one machine at a time to becoming an automation engineer who manages many machines as code.

Holding RHCSA is a prerequisite #

RHCE is an exam where the certification is only awarded if you hold a valid RHCSA at the time you sit. Since about half the exam weight is “automating RHCSA tasks with Ansible,” not knowing RHCSA’s manual tasks means not knowing what you’re supposed to automate. We recommend working through the RHCSA series before starting this track.

Who gets value from it #

Exam structure #

The surface-level facts about the RHCE (EX294) exam are worth committing to memory.

The decisive difference from RHCSA #

RHCSA had you work by hand on a single system, but RHCE has you write playbooks on a control node to configure multiple managed nodes. The unit of work is not a command but a playbook file, and the idempotency that the result stays the same no matter how many times you run the same playbook is the crux of grading. Also, the ability to quickly look up module usage with ansible-doc is what decides your score in an environment without internet.

ansible-navigator vs ansible-playbook #

The latest RHCE environment lets you run playbooks two ways.

• ansible-playbook. The traditional runner. Lightweight, familiar, with simple output.
• ansible-navigator. A runner based on an execution environment (container). run -m stdout produces output similar to the traditional runner.

In the exam you can use whichever of the two you’re comfortable with, but navigator may be the default depending on the environment, so we’ll learn both execution styles and the ansible-navigator run -m stdout option in advance.

Exam domains #

The RHCE scope is laid out by domain in the official exam objectives (EX294 objectives). This series maps to them as follows.

In particular, RHCSA automation (#14–#17) accounts for half the exam weight, so we’ll firm up the Ansible syntax in the earlier posts and then bring it all together across these four.

Study strategy #

1) Build out a control node and managed nodes yourself #

RHCE deals with multiple nodes, so we’ll set up one control node and several managed nodes from three or four VMs to practice. The person who has built inventory, SSH keys, and become by hand is the one who stays steady on exam day.

2) Always verify idempotency #

Get into the habit of running a playbook you wrote twice and checking that the second run reports changed as 0. The feel for swapping a task that breaks idempotency (overusing command/shell, for example) for a module is the crux of RHCE.

3) ansible-doc as your weapon #

Since there’s no internet, ansible-doc <module> is your only reference. The habit of quickly finding module names, key options, and the EXAMPLES at the bottom of the doc saves time.

4) Save mock exams for the back half #

After one loop through this series, you’ll find a full-scale mock exam in #19. We recommend the flow of solving it on a 4-hour timer and checking idempotency and persistence.

Registration and the testing environment #

Registration steps #

1. Buy EX294 or a learning subscription on the Red Hat training portal
2. Choose your delivery method. Test center (Kiosk) or Red Hat Remote Exam
3. Book your exam date, and for a Remote Exam, run the system compatibility check in advance

Preparing for the Remote Exam #

• ID — A passport with English Romanization is safest
• Testing environment — Clear your desk, use a single monitor, and block outsiders from entering
• Boot environment — You sit the exam by booting the provided live image from a USB, so you need a bootable PC and a stable wired network

Wrap-up #

What this post locked in:

• RHCE (EX294) is an Ansible automation hands-on certification. An exam that configures multiple systems consistently with playbooks
• Holding a valid RHCSA is a condition for certification. 4 hours / 210/300 (70%) / valid 3 years / no internet (ansible-doc allowed)
• Exam domains. Environment and inventory, playbooks and variables and templates, control flow and error handling and Vault, roles and collections and system roles, RHCSA automation
• The two execution styles, ansible-navigator (run -m stdout) and ansible-playbook
• Study strategy. Multi-node setup. Always verify idempotency. ansible-doc as your weapon. Save mock exams for the back half

Next — Inventory #

The exam structure is locked in. Now we go into inventory, which defines which hosts Ansible will handle.

In #2 Inventory: static, dynamic, group/host_vars, we’ll build and work through the host and group definitions of a static inventory, the structure for splitting variables with group_vars and host_vars, the concept of dynamic inventory, and the “apply this task only to this group” type that comes up often on the exam.