Failed Red Hat RHCE? Here's Your Recovery Plan

Pro tip: Contact the exam provider directly for their specific retake policy.

• Fixing a system by hand and then writing a playbook that assumes the manual fix. Red Hat replays your playbooks against freshly installed systems, so the manual step never happens during grading.
  Rebuild your managed nodes from clean images and run only your playbooks against them. If anything fails, the playbook is incomplete, not the lab.
• Writing playbooks that are not idempotent, usually by driving everything through the command or shell module. A second run reports changes and can undo earlier work during a replay.
  Reach for a purpose-built module first. Where command or shell is unavoidable, add creates, removes, or changed_when so the task reports honestly on a repeat run.
• Calling a module by its short name when it lives in a collection that is not in the default search path, producing a module not found error mid-run.
  Use the fully qualified collection name, and rehearse browsing installed collections in ansible-navigator so you can find the correct name inside the exam without internet access.
• Building the whole answer as one long playbook when the task asks for a role, or building a role with a directory layout that Ansible will not resolve.
  Practise the role skeleton from memory: tasks, handlers, defaults, vars, files, templates, meta. Call the role from a small site playbook and confirm it resolves without absolute paths.
• Encrypting variables with Ansible Vault and then leaving no way for a replay run to supply the password, so every vaulted task fails during grading.
  Rehearse unattended runs with a vault password file or the configured password source, and verify the playbook completes with no interactive prompt at all.
• Ignoring the ansible-navigator objectives and preparing only with ansible-playbook. The published objectives require running playbooks with navigator, modifying ansible-navigator.yml, and using navigator to find modules and create inventories.
  Run every practice playbook through ansible-navigator for at least two weeks so the interface, the execution environment, and the log output are familiar.
• Skipping the Git and Visual Studio Code objectives because they feel peripheral. Cloning a repository, adding files, and running a playbook in a development container are all on the published list.
  Spend one week working exclusively from the editor: clone, write, push, configure navigator from inside VS Code, and run a playbook using an Ansible development container.
• Forgetting that EX294 still assumes RHCSA competence. The objectives open by requiring all tasks expected of a Red Hat Certified System Administrator, including analysing simple shell scripts.
  Automate the RHCSA objective list itself: repositories, services, firewall rules, file systems, storage devices, file content, archiving, scheduling, security, users, and groups.
• Assuming a current RHCSA is not needed because you passed EX294. Red Hat Certified Engineer in Ansible requires both, and an expired RHCSA cannot be renewed and must be earned again from scratch.
  Check your status at rhtapps.redhat.com/verify before booking EX294, and note that passing EX294 while current renews your RHCSA for another three years.

• RHCSA is prerequisite
• Master Ansible automation completely
• Study playbooks, roles, and collections
• Practice with Red Hat Ansible Automation Platform
• Focus on automation at scale scenarios