- What This Cheat Sheet Covers (and What It Does Not)
- EX436 Exam Facts at a Glance
- The Nine Objective Lines, Decoded
- Cluster Build and Fencing Essentials
- Failover Services and Service Behavior
- Storage and GFS2 Quick Reference
- Reboot Persistence and Grading Reality
- Booking, Retake and Renewal Sheet
- Sequencing Your Prep Around the Objectives
- Frequently Asked Questions
- EX436 is one three-hour, hands-on exam on RHEL High Availability Add-On administration, graded against objective criteria.
- Every configuration must survive a reboot, so enable services and verify state after restarting nodes.
- Red Hat's outline lists nine unweighted objective lines; none is officially weighted by percentage.
- The standard program-wide exam list price is USD500, but your regional booking cart controls the actual price.
What This Cheat Sheet Covers (and What It Does Not)
This page is a one-sitting review of the facts that matter for the Red Hat Certified Specialist in High Availability Clustering exam, EX436. It is built from Red Hat's published exam page, its program guide and the training FAQ, so it sticks to what those sources say. Where Red Hat does not publish something, this sheet says so rather than guessing.
Two things are deliberately absent. First, there are no pass-rate figures or task counts, because Red Hat does not publish them and unverified numbers would only mislead you. Second, there are no recalled exam questions. EX436 is a performance-based exam, and any study material you use, including ours, should be original practice built around the published objectives.
If you are new to the credential itself, start with What Is High Availability Clustering Certification? and come back here for the compressed review. For a longer preparation plan, the High Availability Clustering Study Guide 2026 goes deeper than a cheat sheet can.
EX436 Exam Facts at a Glance
| Item | What Red Hat Publishes |
|---|---|
| Exam code | EX436 |
| Issuer and delivery | Red Hat, Inc., through Red Hat exam delivery |
| Format | One three-hour, hands-on section on RHEL High Availability Add-On administration |
| Grading | Outcomes graded against objective criteria; configurations must survive reboot |
| Prerequisites | RHCSA or RHCE recommended; neither is mandatory |
| Training | RH436 or equivalent experience recommended; class attendance optional |
| Standard list price | USD500 program-wide; regional booking-cart price controls |
| Delivery options | Remote, testing center or classroom, subject to booking availability |
| Results timing | Exam page: usually three U.S. business days; program guide allows five business days |
| Credential currency | Three years under the current framework |
For eligibility questions in more detail, see High Availability Clustering Requirements 2026. For the money side, the High Availability Clustering Certification Cost 2026 breakdown covers the budgeting angle.
The Nine Objective Lines, Decoded
Red Hat's current outline lists nine first-level objective entries. They are unweighted, and nine is simply the count of lines preserved from the published outline, not an issuer-declared official domain count. Notice that logging and monitoring appear as separate entries, and growing a GFS2 filesystem is displayed separately from configuring GFS2.
- Configure a high-availability cluster
- Configure cluster fencing
- Configure cluster logging and monitoring
- Configure cluster monitoring
- Configure a clustered fail-over service
- Configure cluster service behavior
- Configure storage
- Configure GFS2 filesystems
- Grow a GFS2 filesystem
The detailed exam outline takes precedence over the shorter seven-item competency summary on Red Hat's certification page. If the two ever look different, trust the detailed outline. A domain-by-domain walkthrough lives in High Availability Clustering Exam Domains 2026: Complete Guide to All 9 Content Areas.
Cluster Build and Fencing Essentials
Domains 1 and 2: Configure a High-Availability Cluster and Cluster Fencing
These two objectives are the foundation. A cluster that forms but cannot fence is an incomplete answer on a hands-on exam, and nothing else in the outline works well until these are solid.
- Know the full node-up sequence: install packages, enable and start the cluster management daemon, authenticate nodes, create the cluster, start it, and enable it to start at boot.
- Be able to inspect cluster state quickly with the pcs status family of commands and know what healthy output looks like.
- Understand quorum: what it means, how node loss affects it, and how to view it.
- Fencing (STONITH) is how the cluster safely removes a misbehaving node. Know how to list available fence agents, view an agent's required parameters, create a fence device, and test it.
- Practice fencing against the lab hardware or virtualization you are given, because agent parameters differ by platform.
Logging and monitoring: two separate lines
Red Hat lists "Configure cluster logging and monitoring" and "Configure cluster monitoring" as distinct entries, so cover both rather than assuming one implies the other. Be comfortable locating cluster logs, adjusting logging behavior, reading status output to diagnose a stuck resource, and configuring the monitoring operations that let the cluster detect a failed resource in the first place.
Failover Services and Service Behavior
Domains 5 and 6: Clustered Fail-Over Service and Service Behavior
This is where a cluster becomes useful. You will be expected to build a service from resources and then control how and where it runs.
- Create resources and group them so that dependent pieces such as a floating IP address, a filesystem and an application start together and in the right order.
- Understand resource agents and how to look up an agent's parameters before creating a resource.
- Control behavior with constraints: location (where a resource prefers or avoids running), ordering (what starts before what) and colocation (what must run together).
- Know resource stickiness and failure-handling options such as migration thresholds and failure timeouts, and how they decide whether a service moves or stays.
- Be able to move, ban, clear and clean up resources, and put nodes in standby, then verify the service actually relocated.
A useful drill: build a small group service, then deliberately break it. Stop the application outside the cluster, power-cycle a node, add a constraint that conflicts with your intent. Reading cluster status after each failure teaches diagnosis faster than building a clean setup repeatedly. How demanding this hands-on style feels is covered in How Hard Is the High Availability Clustering Exam?
Storage and GFS2 Quick Reference
Domains 7, 8 and 9: Storage, GFS2 Filesystems and Growing GFS2
Three of the nine objective lines are storage-related, so this area is a large share of the published outline even though the lines are not weighted.
- Storage: prepare shared block storage that all cluster nodes can see, and understand how it ties into the services that depend on it.
- GFS2 is a cluster filesystem designed for concurrent access from multiple nodes, which is different from a filesystem mounted by only one node at a time.
- Know the prerequisites for GFS2: cluster membership, a working lock manager, and fencing, since lock safety depends on being able to remove a failed node.
- Know the key format-time decisions, including lock protocol, lock table naming that matches the cluster, and the number of journals, which generally corresponds to the nodes that will mount the filesystem.
- Be able to mount GFS2 as a cluster-managed resource so it comes up on the right nodes automatically.
- Growing a GFS2 filesystem is its own objective line: understand how to extend the underlying storage first, then grow the mounted filesystem online, and verify the new size from more than one node.
Key Takeaway
Treat "Grow a GFS2 filesystem" as a separate skill, not a footnote to GFS2 setup. Rehearse the extend-storage-then-grow sequence on a live, mounted filesystem until you can do it and verify it without consulting notes.
Reboot Persistence and Grading Reality
Red Hat states that EX436 outcomes are graded against objective criteria and that configurations must survive reboot. That single sentence should shape your habits more than any command list.
- Enable, don't just start. A cluster or service that is running now but not enabled will disappear after a restart.
- Reboot-test before you finish. If time allows, restart nodes and confirm the cluster reforms, resources land where intended and shared storage mounts.
- Check the end state, not the process. Grading evaluates results, so a working outcome matters more than the elegance of how you got there.
- Persist what you change. Anything configured outside the cluster tooling, such as firewall rules, SELinux settings or device configuration, needs to be made permanent.
Booking, Retake and Renewal Sheet
| Topic | What to Remember |
|---|---|
| Price | USD500 is the program-wide standard list price; the regional booking-cart amount is what you actually pay |
| Remote delivery | Requires LiveUSB, a successful compatibility test and required identity and hardware checks |
| Availability | Remote, testing-center and classroom delivery all depend on booking availability |
| Retake | Eligible unsuccessful first individual attempts receive one free retake under Red Hat's training policies, subject to eligibility periods and scheduling restrictions |
| Results | Total scores per the exam page; the handbook also describes objective-area feedback; no task-by-task detail |
| Renewal | Current for three years; renew through the original exam or qualifying same-level or higher-level credentials |
Two caveats are worth keeping in mind. First, results timing differs between sources: the exam page says usually three U.S. business days, while the program guide allows five, so plan for the longer window. Second, Red Hat's legacy renewal page still uses older non-expiring terminology and narrower specialist wording. For anything renewal-related, consult the current handbook, the dated framework and your active transcript rather than that legacy page alone. If you hold a pre-framework credential, the FAQ says updated renewal and mapping rules apply to your active transcript after you pass a new exam following May 11, 2026.
Scheduling logistics are covered in High Availability Clustering Exam Dates 2026, and score-related expectations in High Availability Clustering Passing Score 2026. Red Hat does not publish a pass mark in the sources used here, so treat any specific number you encounter elsewhere with suspicion. The same goes for the High Availability Clustering Pass Rate 2026 discussion, which explains why unverified statistics are left out.
Sequencing Your Prep Around the Objectives
Because the outline is unweighted, sequence by dependency rather than by guessed importance. Each stage builds on the one before it:
Cluster and Fencing Foundation
- Build a multi-node cluster from scratch repeatedly until it is routine
- Create and test a fence device before anything else
- Practice reading status, quorum and log output
Services and Behavior
- Build grouped services with an address, storage and application
- Add location, ordering and colocation constraints and prove they work
- Force failures and confirm the cluster responds as intended
Shared Storage and GFS2
- Provision shared storage, then format and mount GFS2 as a managed resource
- Grow a mounted GFS2 filesystem and verify from multiple nodes
Timed, Reboot-Verified Runs
- Run full-length three-hour mock projects from a blank environment
- Finish every run with a reboot test and fix whatever did not persist
Mock projects should be your own original scenarios built from the published objectives, not reconstructions of real exam tasks. If you want structured practice, try the High Availability Clustering practice tests and use the main practice site to check your recall of the concepts behind each objective line. For the full curriculum background, see High Availability Clustering Training.
Who this credential serves
The skills here map to administrators who run Red Hat Enterprise Linux systems where downtime is costly: infrastructure, operations and platform teams responsible for shared services and clustered storage. Whether that translates into a career move depends on your market, and no source here supports promising a salary change or guaranteed employment. For evidence-based discussion, see the High Availability Clustering Salary Guide, the Is the High Availability Clustering Certification Worth It? analysis and the High Availability Clustering Jobs overview.
Frequently Asked Questions
It is one three-hour, hands-on section covering RHEL High Availability Add-On administration. You configure real systems rather than answering multiple-choice questions, and results are graded against objective criteria.
No. Red Hat recommends RHCSA or RHCE but does not make either mandatory. RH436 or equivalent experience is also recommended, and attending the class is optional.
Red Hat's outline publishes nine first-level objective lines. They are unweighted, so nine is a line count rather than an issuer-declared official domain count, and no percentages are published.
Eligible unsuccessful first individual attempts receive one free retake under Red Hat's training policies, subject to purchase or subscription eligibility periods and scheduling restrictions. Confirm your eligibility when you book.
Certifications are current for three years under the present framework. Renew before expiry by retaking the exam or earning a qualifying same-level or higher-level credential. Check the current handbook and your active transcript, since a legacy renewal page uses older wording.