RHCE exam-day guide
RHCE · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring an unexpired, original ID whose name matches your exam registration exactly. Accepted ID types vary by location and delivery format - confirm the list with Red Hat before exam day.
Your Red Hat account credentials and exam appointment confirmation
Know the username/password you registered with and have the confirmation email or appointment number handy. You will likely need to sign in before the exam timer starts.
The published exam objectives, printed once for study and then set aside
The EX294 objectives list the exact skill domains: inventories and config files, ad hoc commands, playbooks, variables and facts, task control (loops, conditionals, handlers), templates, roles, collections, Ansible Vault, and using modules for packages, services, users, storage, firewall, scheduling, and system roles. Treat that list as your scope document - nothing outside it should consume study time.
A working practice lab
One control node plus at least two managed nodes running the same major RHEL version as the exam, with ansible-core installed and SSH key-based access working. If you cannot rebuild it from scratch in under 15 minutes, rebuild it now.
The ability to find answers offline
The exam is effectively closed to the internet, so drill ansible-doc , ansible-doc -l, ansible-doc -s, and read /usr/share/doc and man pages. Practise looking up a module's parameters without a browser.
Hands-on fluency with the core task patterns
Be able to write, unaided: an ansible.cfg and static inventory with groups and group_vars; a playbook using loops, conditionals, handlers, and registered results; a Jinja2 template deployed with the template module; an encrypted variable via ansible-vault; a role scaffolded with ansible-galaxy; a collection installed and referenced; and plays that configure packages, services, users, cron, storage, and firewalld.
A stable network connection and backup plan
Wired ethernet if possible, plus a known fallback (phone hotspot) if your session is remote. Test the connection from the exact spot you will sit in.
Webcam, microphone, and a second device if your session is remote-proctored
Remote deliveries usually require a room scan and proctor contact. Whether a phone is permitted as a second device depends on the delivery format - confirm with the provider.
A quiet, private room with a cleared desk
Remove notes, books, extra monitors, and wall clutter within camera range if proctored remotely. Have water within reach in case leaving the desk is restricted.
A written time budget
Confirm the exam duration with Red Hat (performance-based engineer exams have historically run about four hours - verify the current figure), then plan to spend roughly the first five minutes surveying, the bulk on tasks in your strongest-to-weakest order, and the last 20-30 minutes re-validating that every change persists and is idempotent.
Plan the day
Re-read the official objectives line by line and mark any domain you cannot do from memory. Spend the remaining study time only on those gaps.
Run one full timed mock: fresh nodes, a self-written task list drawn from the objectives, no browser, no notes. Grade yourself on whether the final system state passes a re-run, not on whether the playbook looked nice.
Confirm logistics: session format (test center vs remote), start time in your own time zone, and the provider's check-in window. Write the time down.
Light review only: vault workflows, handler notification, when/loop syntax, role directory structure, ansible.cfg precedence (ANSIBLE_CONFIG, ./ansible.cfg, ~/.ansible.cfg, /etc/ansible/ansible.cfg). Do not start a new topic.
Test the hardware: camera, microphone, connection, and the proctoring software if one is required. Charge everything. Lay out your ID and login details.
Sleep a full night. Fatigue costs more points on a four-hour practical than one more hour of review gains.
Eat, hydrate, and clear the desk. Close every application except what the exam requires; background updates mid-exam are a real failure mode.
Sign in and start check-in early - if the provider publishes an early-arrival window, use it, since identity verification and room scans take time.
First pass: read every task and note the ones you can finish in under five minutes. Do those first to bank points, then return to the harder ones.
Build the foundation before the tasks: set up your working directory, inventory, and ansible.cfg once, then reuse them. Verify connectivity to all managed nodes before writing long playbooks.
Work incrementally: syntax-check, run against one host, then run against all. Use --check and --diff where safe, and confirm results with ad hoc commands rather than trusting the play recap.
Reserve the final 20-30 minutes to re-run each playbook and confirm idempotence, confirm services are enabled as well as started, confirm files persist after reboot if required, and confirm nothing was left half-configured.
Rules to check
Bring government-issued photo ID with a name matching your registration exactly; if your legal name differs from the name on the booking, fix it with the provider before exam day, not at check-in.
The exam is a closed environment: no internet, no personal notes, no books, and no communication with others. Rely on the documentation installed on the exam system. Confirm the precise allowed-resource list with the provider, since it can vary by delivery format.
Do not attempt to reach outside the exam environment, install unapproved tooling, or interfere with the grading mechanism. Grading is automated against the final state of your systems, so a clever workaround that leaves the system wrong scores zero.
Breaks and desk-leaving rules differ between test-center and remote delivery, and the clock generally does not stop. Ask your proctor or confirm the policy in advance rather than assuming.
Scoring is performance-based: you are graded on whether the required end state exists on the machines, not on how elegant your playbooks are. Confirm the published passing score with Red Hat rather than relying on secondhand figures.
Attempt every task you can - a partially configured system may still satisfy some checked conditions, while an untouched task almost certainly earns nothing.
Results are delivered by email after grading, typically within a few business days; confirm the current turnaround and any retake policy with the provider.
Do not disclose, record, or redistribute exam content. Treat the tasks you see as confidential under the certification agreement.