- What the Credential Actually Is
- The Technology Behind It: RHEL High Availability Clustering
- How the EX436 Exam Works
- The Nine Published Objectives
- What Hands-On Competence Looks Like
- Who Benefits From It
- Prerequisites and Training Path
- Fees, Retakes, and Renewal
- A Domain-Ordered Preparation Sequence
- Frequently Asked Questions
- Red Hat Certified Specialist in High Availability Clustering is earned by passing the performance-based EX436 exam, issued by Red Hat.
- EX436 is one three-hour hands-on section; configurations must survive a reboot to count.
- The published outline lists nine objectives, from cluster setup and fencing to growing GFS2 filesystems.
- RHCSA or RHCE is recommended, not mandatory; RH436 is recommended but class attendance is optional.
What the Credential Actually Is
When people ask "what is a High Availability Clustering?" in the context of this site, they mean one specific credential: the Red Hat Certified Specialist in High Availability Clustering. It is issued by Red Hat, Inc., and it is earned by passing the exam coded EX436. Red Hat both governs the credential and delivers the exam, so there is no separate third-party testing body to track down.
"High Availability Clustering" is simply the natural short label we use for this certification. It is not an official acronym coined by Red Hat, and it should not be confused with any other credential that happens to share similar wording. Everything on this page concerns the Red Hat specialist credential and its EX436 exam.
In plain terms, the certification verifies that you can build and administer a high-availability cluster on Red Hat Enterprise Linux using the High Availability Add-On. You prove it by doing the work on live systems, not by answering multiple-choice questions. If you want the broader overview of the credential's scope, our High Availability Clustering Certification page covers the big picture, and What Is High Availability Clustering Certification? goes deeper on what the badge represents.
The Technology Behind It: RHEL High Availability Clustering
A high-availability cluster is a group of servers (nodes) that cooperate so that a workload keeps running even when one node fails. Instead of a human restarting a database or web service on another machine at 3 a.m., the cluster detects the failure, isolates the broken node, and starts the service somewhere healthy. The RHEL High Availability Add-On provides the tooling to configure and manage this behavior.
Several ideas recur throughout the exam and throughout real-world cluster work:
- Membership and quorum: nodes must agree on who is in the cluster, and the cluster must know when it has enough votes to act safely.
- Fencing: a failed or unresponsive node must be reliably cut off from shared resources before its services are recovered elsewhere. Without fencing, a cluster risks data corruption.
- Resources and resource groups: services such as a floating IP, a filesystem mount, and an application are defined as managed resources that start in the right order on the right node.
- Constraints: rules that control where resources may run, what must run together, and what must start first.
- Shared storage: clustered workloads often depend on storage that more than one node can reach, including clustered filesystems like GFS2.
How the EX436 Exam Works
EX436 is a performance-based, hands-on exam. There is a single three-hour section covering RHEL High Availability Add-On administration. You are given systems and a set of tasks, and you configure them to meet stated requirements. Results are graded against objective criteria, meaning the grading checks whether your configuration actually produces the required outcome rather than whether you recited the right command.
Two format realities shape how you should prepare:
- Configurations must survive a reboot. A cluster that works until the first restart does not pass. Enabling the right services, persisting settings, and verifying state after a reboot are part of every task, not an optional extra.
- The exam page does not specify an exam-specific documentation allowance. Do not assume what reference material will or will not be available. Verify the rules for your booked session, and build enough command-line fluency that you are not dependent on looking things up.
Red Hat's live exam page follows the most recent available product version without naming a specific RHEL release in its main description. That means you should not label the exam by a release number based on a training course alone. Practice on a current RHEL environment and confirm details against the official exam page when you book.
For a candid look at how demanding this format feels, see How Hard Is the High Availability Clustering Exam?. For score-related questions, our passing score guide explains what is and is not publicly documented. Red Hat does not publish verified pass marks or pass-rate statistics, and we do not invent them; the pass rate article explains how to think about that gap.
The Nine Published Objectives
The detailed Red Hat exam outline lists nine first-level objectives. These are unweighted: Red Hat does not publish percentages for them, and nine is the count of published lines rather than an issuer-declared "official domain count." Where the detailed outline and the shorter seven-item competency summary differ, the detailed outline takes precedence.
| # | Objective | What it centers on |
|---|---|---|
| 1 | Configure a high-availability cluster | Building the cluster: nodes, authentication, membership, quorum behavior |
| 2 | Configure cluster fencing | Fence devices, node isolation, safe failover prerequisites |
| 3 | Configure cluster logging and monitoring | Making cluster events visible and traceable |
| 4 | Configure cluster monitoring | Observing cluster and resource state |
| 5 | Configure a clustered fail-over service | Defining resources and groups that move between nodes |
| 6 | Configure cluster service behavior | Constraints, ordering, stickiness, and failure handling |
| 7 | Configure storage | Shared and clustered storage the services depend on |
| 8 | Configure GFS2 filesystems | Creating and mounting clustered filesystems |
| 9 | Grow a GFS2 filesystem | Expanding an existing clustered filesystem safely |
Notice that logging and monitoring appear as separate entries, and that growing a GFS2 filesystem is listed apart from configuring one. Those separations are preserved from the published outline. For a deeper walkthrough of each, read High Availability Clustering Exam Domains: Complete Guide to All 9 Content Areas.
Cluster Setup and Fencing (Objectives 1 and 2)
These two objectives are the foundation. Everything else assumes a healthy, correctly fenced cluster.
- Bring nodes together into a functioning cluster and confirm membership.
- Understand how quorum affects what the cluster is willing to do.
- Configure fencing so a misbehaving node is reliably isolated.
- Verify that fencing actually triggers, not merely that it is defined.
Services and Behavior (Objectives 5 and 6)
Here you make the cluster do useful work and control how it does it.
- Define resources that together deliver one service, such as an address, storage, and an application.
- Use constraints to control placement and start order.
- Shape failure behavior so the cluster responds predictably to problems.
Storage and GFS2 (Objectives 7, 8, and 9)
Storage objectives tie the cluster to data that multiple nodes can reach.
- Prepare storage appropriate for clustered use.
- Create and mount a GFS2 filesystem across nodes.
- Grow an existing GFS2 filesystem without disrupting the cluster.
What Hands-On Competence Looks Like
Because grading is objective and outcome-based, the useful mental model is a checklist of states your systems must be in when time expires. A few habits separate prepared candidates from those who struggle:
- Verify after every task. Check cluster status, resource state, and constraint behavior before moving on. A misconfiguration discovered at minute 170 is far more expensive than one caught at minute 20.
- Test failover deliberately. Do not assume a resource group will relocate; move it, stop a node, and watch what happens.
- Reboot and re-check. Since persistence is part of the grading criteria, include a reboot check in your own workflow during practice.
- Read the requirement literally. Tasks specify outcomes. Meet the stated outcome exactly rather than building something more elaborate than asked.
Who Benefits From It
This credential speaks to people who run Linux infrastructure where downtime is expensive. Typical roles that value cluster competence include Linux systems administrators, infrastructure and platform engineers, site reliability and operations staff, and consultants supporting RHEL-based enterprise environments. Organizations running critical databases, application tiers, or shared-storage workloads on Red Hat Enterprise Linux are the natural audience for the skill set.
We deliberately avoid quoting salary numbers or promising outcomes here. Certification does not by itself cause a raise or guarantee a job; it is evidence of demonstrated skill that sits alongside experience. If you want to weigh the investment, our ROI analysis and salary guide discuss how to evaluate market evidence responsibly, and High Availability Clustering Jobs looks at the kinds of roles where this skill shows up.
Prerequisites and Training Path
Red Hat recommends that candidates hold RHCSA or RHCE before attempting EX436, but neither credential is mandatory. The recommendation exists because clustering builds on solid RHEL administration: storage, networking, services, SELinux, and the firewall all interact with a cluster. If those fundamentals are shaky, cluster troubleshooting becomes much harder.
On the training side, RH436 (Red Hat High Availability Clustering) is the recommended course. It is a four-day course, and its source material is built on RHEL 8.3. Two important cautions apply:
- Course attendance is optional. Equivalent hands-on experience is an accepted route.
- RH436 is preparation curriculum. Its topics do not define exhaustive exam coverage, and its RHEL 8.3 basis should not be treated as proof of which release your booked exam uses.
Our requirements guide covers eligibility in detail, and High Availability Clustering Training compares learning routes.
Fees, Retakes, and Renewal
Exam fee and booking
The program-wide standard Red Hat exam list price is USD 500. That is a program-level figure, not an exam-specific checkout quotation; the regional price shown in your booking cart is the one that controls. Delivery options include remote, testing center, and classroom, all subject to booking availability. Remote candidates need a LiveUSB, a successful compatibility test, and must pass the required identity and hardware checks. Our certification cost breakdown and exam dates guide go further on pricing and scheduling.
Retake policy
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. Read the current policy before assuming you qualify.
Results timing
Red Hat's guidance on results timing differs by source. The exam page says results usually arrive within three U.S. business days, while the program guide allows up to five business days. Score reporting provides total scores, and the handbook also describes objective-area feedback, but neither provides task-by-task performance details.
Renewal
Certifications are current for three years. You can renew before expiry by retaking the original exam or by earning a qualifying same-level or higher-level credential under the current framework. For credentials earned before the framework change, Red Hat's FAQ says updated renewal and mapping rules apply to your active transcript after you pass a new exam following May 11, 2026.
A Domain-Ordered Preparation Sequence
Rather than a generic study schedule, sequence your preparation by dependency: later objectives rely on earlier ones working. One reasonable ordering follows, to be adapted to your pace.
Cluster build and fencing
- Stand up a multi-node virtual cluster from scratch, repeatedly.
- Configure fencing early and prove it works by triggering it.
Logging, monitoring, and fail-over services
- Make cluster events visible, then build a multi-resource service.
- Practice moving the service and simulating node failure.
Service behavior and constraints
- Control placement and start order, then tune failure handling.
- Reboot nodes and confirm everything persists.
Storage, GFS2, and growth
- Prepare shared storage, create and mount GFS2, then grow it.
- Run timed full-environment rehearsals using original scenarios.
For more structure, our study guide expands this plan, and the cheat sheet offers a compact review. When you are ready to check readiness, try our practice tests.
Key Takeaway
Treat EX436 as a build-and-verify exam. Practice constructing the whole environment, test failover on purpose, and reboot to confirm persistence before you call any task done.
Frequently Asked Questions
It is a Red Hat credential earned by passing the hands-on EX436 exam. It verifies that you can configure and administer clusters using the RHEL High Availability Add-On, including fencing, fail-over services, and GFS2 storage.
No. EX436 is a single three-hour, performance-based section. You configure real systems to meet stated requirements, and the results are graded against objective criteria. Configurations must also survive a reboot.
Red Hat recommends RHCSA or RHCE, but neither is mandatory. The RH436 course is also recommended, though attending it is optional if you have equivalent experience.
Red Hat's program-wide standard exam list price is USD 500, but the regional price in your booking cart controls what you actually pay. Eligible unsuccessful first individual attempts may qualify for one free retake under current policy.
Certifications are current for three years. Renew before expiry by retaking the exam or earning a qualifying same-level or higher-level credential. Check your active transcript and the current framework, since an older renewal page uses outdated terminology.
If you want a quick definition-focused companion to this article, see What Is High Availability Clustering?, and when you are ready to test your skills, head back to the main practice site.