Cyber Security — Program 05

RHCE — Red Hat Engineer (Ansible)

Red Hat only awards RHCE to someone who already holds a current RHCSA — you can sit EX294 first, but the certificate is not issued until EX200 is passed. So we take RHCSA holders, or administrators who pass our own RHCSA mock at the entry test. Letting anyone else in produces someone who spends eight weeks debugging their Linux gaps instead of learning Ansible. The entry test is the kindest part of this programme.

2 months · 8 weeks 4 live hours a week 8 lab hours a week Level Intermediate

( Who it is for )

You need

  • A current RHCSA, or pass our RHCSA mock at the entry test. This one is not waived — see below.

It prepares you for

  • Automation Engineer, DevOps engineer, senior Linux administrator
  • Red Hat EX294

( Curriculum — 8 weeks )

Phase 01Weeks 1–2

Ansible and playbooks

From ad-hoc commands to playbooks that can be run twice safely.

  • Control node and managed hosts
  • Inventories and host variables
  • ansible.cfg and privilege escalation
  • Plays, tasks and the module mindset
  • Idempotency, and how to prove it
  • Checking with --check and --diff
Phase 02Weeks 3–4

Data and templates

Playbooks that adapt to the machine they land on.

  • Variable precedence in practice
  • Facts and custom facts
  • Filters, conditionals and loops
  • Jinja2 templating
  • Handlers and notification
  • Blocks, error handling and tags
Phase 03Weeks 5–6

Roles and real administration

Every task from RHCSA, now written as code.

  • Writing a role from scratch
  • Galaxy and collections
  • RHEL system roles
  • Users, storage and services at scale
  • Firewall, SELinux and scheduled jobs
  • Repositories and packages
Phase 04Weeks 7–8

Security, structure, exam

Keeping secrets out of your repository, then a full rehearsal.

  • Ansible Vault
  • Delegation and async tasks
  • import versus include
  • A reusable project layout
  • Troubleshooting a play that fails on one host
  • Full timed mock exam

The capstone.

A set of machines that must end up in a given state — written as a role, idempotent, and run twice against clean hosts. Changed-on-second-run is a fail, however good the YAML looks. That is the exam, and it is the job.

You finish with: A Git repository of roles that provision an environment from scratch · A documented, reusable project layout · A timed mock result against the published objectives · Readiness to book EX294.

Next batch enrolling

Enroll ↗
← All Cyber Security programs Foundations → Blue Team → Red Team → RHCSA →
WhatsApp