“"The practice exams helped me strengthen my Ansible and Linux administration skills. The explanations made complex topics much easier to understand."”
Sneha Reddy
Linux System Administrator
EX294 isn’t a question bank you click through — it’s a hands-on exam built entirely around Red Hat Ansible Automation Platform. You’re given access to several live systems and a list of tasks described as end states (“ensure the web_servers group is running httpd, the service is enabled, and index.html is deployed from a template containing the hostname”) rather than as step-by-step instructions. You write and run the playbooks; Red Hat’s scoring rebuilds the target systems from scratch and checks whether your playbooks actually produce the specified result after a fresh reboot.
The exam runs 240 minutes. There’s no internet access and no outside notes or books permitted, though the documentation that ships with the product is available on the exam system itself — which means knowing how to search Ansible’s built-in docs under time pressure matters as much as knowing the modules.
One thing a lot of older prep resources miss: Red Hat’s current objectives explicitly call out ansible-navigator (not just the older ansible-playbook command), basic Git operations (cloning a repo, committing playbooks), and working inside VS Code, including running playbooks through an Ansible development container. If your practice has only ever used ansible-playbook from a bare terminal, you’re missing part of the current exam environment.
Red Hat does not publish percentage weightings for EX294 — if you see a page claiming “25% playbooks, 20% roles,” that breakdown isn’t coming from Red Hat. What Red Hat does publish is the list of objective areas below, taken directly from the official exam objectives.
Objective Area | What It Covers |
|---|---|
RHCSA Foundations | Essential tools, running systems, local storage, file systems, user/group management, basic security, reading simple shell scripts |
Core Ansible Concepts | Inventories, modules, variables, facts, loops, conditionals, plays, playbooks, configuration files, roles |
Configuring Ansible | Creating/modifying ansible.cfg and ansible-navigator.yml, building static inventories |
Managed Node Setup | Distributing SSH keys, configuring privilege escalation, deploying files to managed nodes |
Running Playbooks | Using ansible-navigator and ansible-playbook, finding and using modules from Content Collections |
Git and VS Code Workflow | Cloning repos, pushing playbooks, configuring ansible-navigator and running playbooks from a dev container inside VS Code |
Writing Plays and Playbooks | Working with common modules, retrieving command output into variables, conditionals, error handling |
Roles and Content Collections | Creating roles with ansible-galaxy init, installing and using roles and Collections |
Automating RHCSA Tasks | Packages/repos, services, firewall rules, file systems, storage devices, file content, archiving, scheduling, security, users/groups |
Managing Content | Jinja2 templates for configuration files, Ansible Vault for protecting sensitive data |
ansible-navigator as the default workflow. A surprising number of candidates prep entirely with ansible-playbook and only discover ansible-navigator’s execution-environment model on exam day. If you haven’t run playbooks through it and used it to browse module docs, you’re relearning your tooling under a clock.
Vault under exam conditions. Encrypting a file with ansible-vault is easy in isolation. Doing it correctly inside a playbook run — managing the vault password file or prompt, re-encrypting after edits, not locking yourself out of your own variables — is where people lose time.
Reboot persistence is graded, not assumed. Red Hat explicitly reruns your playbooks against freshly installed systems and checks state after a reboot. A playbook that “worked” interactively but depended on a manual step you did by hand, or on cached facts that won’t exist on a clean system, will fail.
Writing roles from nothing. Using a role someone else built is a different skill from running ansible-galaxy init and building out tasks/main.yml, templates/, defaults/, and handlers/ correctly from a blank directory structure — which is what the objectives actually test.
Error handling beyond the happy path. block/rescue, failed_when, and ignore_errors show up more in scenario-based tasks than most study plans account for, because it’s easy to practice modules in isolation without ever forcing a failure case.
Because EX294 describes end states rather than steps, the most useful practice format mirrors that: give yourself a one- or two-sentence goal (“deploy a role named webserver that installs and starts nginx with a templated config, applied to the web_servers group”) and write the playbook from an empty file, timed, without referencing a previous solution. Multiple-choice-style recall questions are a poor fit for this exam — they’ll tell you whether you remember a module name, not whether you can structure a working role under pressure If you're preparing for Designing Cisco Enterprise Networks (ENSLD), try our online practice test.
After you finish a scenario, don’t just check whether the output looked right — tear down and rerun the playbook against a clean system if you can, or at minimum reboot and re-verify. That single habit catches more of the mistakes that actually fail people than anything else in prep.
Spend deliberate time practicing with ansible-navigator’s doc lookup rather than a browser, since that’s the only reference you’ll have available during the session.
Playbooks that pass on first run but aren’t idempotent or don’t survive a reboot
Roles applied to the wrong host group in the inventory, so the task technically ran but not where it was supposed to
Losing time fumbling with an unfamiliar editor or dev-container setup instead of a rehearsed workflow
Misreading what the end state actually requires — performance-based items generally don’t offer partial credit for “close enough”
Vault password handling that locks the candidate out of their own encrypted variables mid-exam
New to Red Hat system administration: You need RHCSA (EX200) first — it’s a hard prerequisite, not a recommendation. Budget several months for RHCSA fundamentals before even starting Ansible-specific prep.
Holds RHCSA, new to Ansible: Most candidates in this position need somewhere in the range of four to eight weeks of focused practice — writing playbooks daily, building roles from scratch, and working through full multi-task scenarios under a timer in the final one to two weeks.
Retaking the exam: Identify exactly which objective area cost you the exam (if your score report gives any indication) and drill that narrowly — most retakes fail on a specific skill gap (roles, Vault, or reboot persistence) rather than a general lack of readiness.
Two things are worth knowing if you studied from older material or are working from guides written more than a year or two ago. First, Red Hat has folded Git and VS Code workflow tasks, plus running playbooks through ansible-navigator and a development container, into the official objectives — these aren’t optional extras layered on top of “classic” Ansible skills anymore. Second, Red Hat’s own exam page now lists the credential earned by passing EX294 as the “Red Hat Certified Advanced System Administrator in Ansible,” which counts toward Red Hat Certified Engineer in Ansible and Red Hat Certified Architect in Ansible — the RHCE name persists as the certification path people recognize, but it’s worth knowing Red Hat has shifted the underlying naming. The exam also tracks the current stable RHEL release (RHEL 9 at present), so expect the objectives and available modules to shift again whenever Red Hat moves the baseline forward.
Last updated on Oct, 30 2026