- The Honest Answer: What Red Hat Publishes About the EX342 Passing Score
- Which Exam We Mean by EX342
- How a Hands-On Troubleshooting Exam Is Scored
- The Persistence Rule: Why a Fix That Does Not Survive Reboot Is Not a Fix
- What Your Score Report Does and Does Not Tell You
- Domain-by-Domain Readiness for Scoring Well
- Results Timing, Retakes and Cost
- Sequencing Your Preparation Around the Eight Domains
- Who Values This Credential
- Frequently Asked Questions
- Red Hat does not publish a numeric EX342 pass mark in the sources reviewed, so any specific cutoff you read online is unverified.
- EX342 is a four-hour hands-on RHEL 10.2 troubleshooting exam, so you earn credit by repairing real systems, not by answering questions.
- Fixes must stay functional across the normal platform lifecycle without manual restoration, so verify every repair after a reboot.
- Results usually arrive in about three U.S. business days per the exam page, though the program guide allows up to five.
The Honest Answer: What Red Hat Publishes About the EX342 Passing Score
Every candidate asks the same question first: what percentage do I need? For the Red Hat Certified Advanced System Administrator in Enterprise Linux exam (EX342), the answer from the sources reviewed for this article is plain: no numeric pass mark is published. The exam page describes total scores, and the certification handbook describes objective-area feedback, but neither states a cutoff you can aim for.
You will find forum posts and third-party sites quoting precise figures. Treat them with suspicion. Unless a number appears in Red Hat's own program guide, exam page or handbook, it is folklore, and folklore about a different Red Hat exam is easy to mistake for facts about this one. This site deliberately omits unverified pass marks, task counts and pass-rate statistics. If you want to understand what the available data does and does not show, see our companion piece, EX342 Pass Rate 2026: What the Data Shows.
Which Exam We Mean by EX342
EX342 here means one thing: the Red Hat Certified Advanced System Administrator in Enterprise Linux exam, issued and delivered by Red Hat, Inc. Under the May 2026 framework this title replaced the older Specialist in Linux Diagnostics and Troubleshooting name. The exam code did not change. Passing EX342 alone earns the advanced administrator credential, and a candidate who holds a current RHCSA (EX200) and then passes EX342 follows the RHCE in Enterprise Linux path.
If you are still orienting yourself, our explainers What Is EX342? and What Does EX342 Stand For? cover the naming history, and EX342 Requirements 2026 walks through recommended background: RH342 or equivalent troubleshooting experience, plus RHCSA or equivalent administration experience.
The objective source for this article is the live Red Hat exam page for RHEL 10.2, reviewed October 14, 2026. Multiple exam versions are in use, and the linked Red Hat document listing objectives by version could not be retrieved during research. We therefore infer nothing from it. Confirm the designated version in your booking or LMS before you study, and do not let legacy RHEL 7 or 8 material override the current RHEL 10.2 page.
How a Hands-On Troubleshooting Exam Is Scored
EX342 is a four-hour, hands-on exam on RHEL 10.2. You are placed in front of systems that are broken and asked to diagnose and repair the problems or, in some cases, gather evidence so a third party can investigate. Relevant product documentation is supplied inside the exam environment, and outside assistance is prohibited.
That format changes what a "score" means. There is no answer key of multiple-choice letters. The exam environment evaluates the state of your systems against what a correct outcome looks like. In practical terms this has three consequences:
- Outcomes beat explanations. A correct diagnosis written in your head earns nothing if the system is still broken. A working fix earns credit even if your route was inelegant.
- Partial progress is not guaranteed to count. Because the exam checks end state, a half-applied repair may leave a service still failing. Finish what you start.
- Collateral damage costs you. A fix that breaks something else, such as loosening security to make a service start, can undo the credit you hoped to earn elsewhere.
For a candid look at how this format compares to other certification exams, read How Hard Is the EX342 Exam? Complete Difficulty Guide 2026.
The Persistence Rule: Why a Fix That Does Not Survive Reboot Is Not a Fix
The single most scoring-relevant statement on the exam page is that configurations and services must remain functional across the normal platform lifecycle without manual restoration. This is a persistence requirement, and it is where capable administrators lose points.
A runtime-only change is the classic trap. If you correct a setting live but never write it to the persistent configuration, the system looks healthy until it restarts, and then the fault returns. Candidates who test only the running state can walk out believing they passed.
Persistence Checks to Build Into Every Repair
Before you move to the next task, confirm that your fix will still be there after a restart or service cycle.
- Services: confirm both the running state and the enablement state, and that the service starts cleanly from a fresh start rather than only from your manual command.
- Mounts and file systems: verify the configuration that applies at boot, not just a mount you performed by hand.
- Network settings: check that the connection profile, not just the live interface, carries your change.
- Security context and policy: confirm labels and policy changes persist, rather than being a temporary relabel or a runtime toggle.
- Authentication: confirm the configuration and any dependent services come back correctly after a restart.
Rebooting the exam system to prove a fix is a legitimate habit, and it costs a few minutes that most candidates can spare inside a four-hour window. Practice it in your labs until it is reflexive.
What Your Score Report Does and Does Not Tell You
After the exam you receive a result. The exam page describes total scores, and the handbook also describes objective-area feedback. Neither source describes task-by-task performance details. In plain terms: expect to learn pass or fail and some indication of how you did by area, but do not expect to see which specific faults you missed or why.
| What You Can Reasonably Expect | What You Should Not Expect |
|---|---|
| A total score outcome as described on the exam page | A published numeric pass mark to measure yourself against |
| Objective-area feedback as described in the handbook | Task-by-task breakdown of what you got right or wrong |
| Notification within the stated results window | A review of your commands or a copy of the broken systems |
This is why a failed attempt requires disciplined self-diagnosis. You will rebuild your picture of the exam from memory and from the area-level feedback. One caution: do not try to reconstruct or share actual exam content afterward. Practice material should be original, built from your own labs rather than recalled tasks.
Domain-by-Domain Readiness for Scoring Well
The eight domains below are the current exam-objective groups. Red Hat does not publish official weights for them, so do not assume any domain counts for more than another. Treat all eight as live. For deeper coverage of each, see EX342 Exam Domains 2026: Complete Guide to All 8 Content Areas.
Domain 1: Understand and employ general methods for troubleshooting
This domain is the method behind every other task: observe, form a hypothesis, test, change one thing, verify.
- Read logs and journal output before touching configuration.
- Change one variable at a time so you know what fixed the problem.
- Use the supplied documentation efficiently rather than guessing.
Domain 2: Diagnose and troubleshoot system startup issues
Systems that will not boot cleanly are a recurring theme in troubleshooting exams, so practice recovering one without panic.
- Understand the boot sequence well enough to tell which stage failed.
- Practice rescue and emergency access and then returning to normal operation.
- Remember that a startup fix must persist across the next boot.
Domain 3: Diagnose and troubleshoot file system issues
Storage and mount faults can block other services, so they often sit upstream of other symptoms.
- Separate device, file system and mount-configuration problems.
- Verify that mount definitions are correct for boot, not only for the current session.
- Check for space, ownership and label issues that mimic service failures.
Domain 4: Resolve package management issues
Broken repositories, damaged packages and dependency problems can look like application faults.
- Inspect repository configuration and package integrity.
- Use verification tools to find altered or missing files.
- Restore the system to a consistent, supported state.
Domain 5: Troubleshoot and fix network connectivity issues
Connectivity problems span addressing, name resolution, routing and firewall behavior.
- Work from the lowest layer upward to isolate the failing layer.
- Confirm that profile-level changes persist, not just live interface edits.
- Check firewall and policy interactions that block otherwise correct configurations.
Domain 6: Diagnose application issues
An application that fails to start or behave often reflects an underlying system fault elsewhere.
- Read service status and logs to find the real cause.
- Consider permissions, security context, ports and dependencies.
- Do not weaken security controls as a shortcut to a working service.
Domain 7: Identify and fix authentication issues
Login and identity failures can stem from configuration, services, time, or account state.
- Distinguish local account problems from centralized identity problems.
- Check the services and configuration that authentication depends on.
- Verify that a fixed login works the way a real user would experience it.
Domain 8: Gather information to aid third-party investigation of issues
Sometimes the right outcome is not a repair but well-collected evidence for someone else to analyze.
- Know what diagnostic data is useful and how to collect it correctly.
- Capture information without altering the evidence you are trying to preserve.
- Present or store it in the form the task requests.
Key Takeaway
Because no domain weights are published, a sensible strategy is breadth first: make sure you can handle at least the common fault in every one of the eight groups before you deepen any single area. A confident repair in six domains beats mastery of two and helplessness in the rest.
Results Timing, Retakes and Cost
Two Red Hat sources give slightly different result timeframes. The exam page says results usually arrive in three U.S. business days, while the program guide allows up to five business days. Plan around the longer window if a deadline depends on your result, and do not assume a delay means a failure.
On cost, the program-wide standard exam list price is USD 500. That is not an exam-specific checkout quotation: the regional price shown in your booking cart controls, so confirm it there. For a fuller breakdown of fees and what else you might spend on, see EX342 Certification Cost 2026: Complete Pricing Breakdown.
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 policy before booking, because eligibility depends on how you purchased the exam. Delivery options include remote, testing-center and classroom formats, all subject to booking availability. Remote candidates need LiveUSB, a successful compatibility test and the required identity and hardware checks, so run that compatibility test well ahead of exam day. Scheduling details are covered in EX342 Exam Dates 2026: Testing Windows, Deadlines & Scheduling.
Sequencing Your Preparation Around the Eight Domains
Since the exam rewards durable, verified fixes across all eight areas, schedule your lab time so each domain gets hands-on repetition and the persistence habit is built early. The plan below assumes you already hold RHCSA-level skills. Our EX342 Study Guide 2026: How to Pass on Your First Attempt expands on each step.
Method and Startup (Domains 1-2)
- Drill the observe-hypothesize-test-verify loop with log reading.
- Practice rescue-mode access and recovering from a failed boot.
- Reboot after every fix to prove persistence.
Storage and Packages (Domains 3-4)
- Break mounts and file systems in your own lab and repair them.
- Damage repositories and packages, then restore a consistent state.
- Check boot-time configuration, not only live state.
Network and Applications (Domains 5-6)
- Fault the network at each layer and isolate it methodically.
- Break services through permissions, ports and security context.
- Resist disabling security controls to force a fix.
Authentication, Evidence and Full Runs (Domains 7-8)
- Repair authentication faults and test as an end user.
- Practice collecting diagnostic evidence cleanly.
- Run timed, mixed-fault lab sessions that mimic a four-hour sitting.
When you want structured, original practice to test your recall of concepts between lab sessions, the EX342 practice tests on the main site are designed around these domains. The EX342 Cheat Sheet 2026 is a useful last-day review of the facts that matter, and the practice test site can help you gauge readiness before you book. Build your own mock projects too: a friend or a second virtual machine can break your lab in ways you did not choose, which is the closest you can get to the real format without using real exam content.
Who Values This Credential
EX342 speaks to employers who run Red Hat Enterprise Linux at scale and need people who can restore service quickly and cleanly: managed service providers, enterprise infrastructure and operations teams, support engineering groups and consultancies that inherit other people's broken systems. The credential signals that you can diagnose under time pressure on a live system, which is different from knowing how to build one. For role patterns, see EX342 Jobs.
On money, be careful. No credential causes a particular salary, and we do not quote earnings figures here without attributable market evidence. Our analysis pieces, EX342 Salary Guide 2026 and Is the EX342 Certification Worth It?, discuss the question qualitatively and without guarantees of pay or employment.
Frequently Asked Questions
The Red Hat sources reviewed for this article do not publish a numeric pass mark for EX342. The exam page describes total scores, and the handbook describes objective-area feedback. Any specific percentage you see elsewhere should be treated as unverified.
No task-by-task performance details are described in the reviewed sources. You can expect total-score and objective-area feedback, which means a failed attempt requires careful self-diagnosis based on your own recollection of the areas that felt weak.
The exam page says results usually arrive in about three U.S. business days, while the program guide allows up to five business days. Plan around the longer window if you have a deadline.
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. Check the policy and your purchase type before relying on it.
The exam requires configurations and services to remain functional across the normal platform lifecycle without manual restoration. A runtime-only change that disappears after a restart can leave the problem unresolved, so verify persistence after each repair.