EX380 Exam Guide: Skills, Preparation Strategy, and Scheduling Decisions
EX380 validates whether you can plan, implement, and manage large-scale Red Hat OpenShift Container Platform deployments in an enterprise. It is aimed at experienced platform and systems professionals who administer OpenShift, containerized applications, identity, storage, automation, and recovery. This guide helps you decide whether your current operational experience is sufficient, which skills need deliberate practice, how to structure preparation, and when to verify scheduling details with Red Hat.
What does EX380 validate?
EX380 is the Red Hat Certified Advanced System Administrator in OpenShift exam. Its central test is practical enterprise administration: can you configure, automate, protect, and recover OpenShift services and workloads rather than simply describe their concepts? Passing earns the Red Hat Certified Advanced System Administrator in OpenShift credential.
Red Hat states that the exam tests the ability to plan, implement, and manage large-scale Red Hat OpenShift Container Platform deployments in an enterprise. That scope is broader than deploying a sample application. Your preparation should therefore include operational decisions, troubleshooting, security configuration, and recovery work performed in a functioning cluster.
The current EX380 exam is based on Red Hat OpenShift Container Platform 4.18. Use documentation and practice environments that match the version identified on the official exam page. If your production experience is on an earlier or later release, verify the current objectives before you commit to a study plan.
Who should consider this exam?
EX380 is best suited to professionals who already administer OpenShift or equivalent container platforms and now need to demonstrate advanced, enterprise-oriented administration. Red Hat identifies platform engineers, system administrators, cloud administrators, enterprise architects, SREs, and DevOps engineers as intended candidates.
Red Hat recommends a current Red Hat Certified Specialist in OpenShift Administration certification or equivalent OpenShift cluster and containerized-application administration skills. Treat that recommendation as a readiness check, not as a substitute for the exam’s stated knowledge areas. Someone who knows Kubernetes theory but has little OpenShift administration practice should first close that operational gap.
The credential can be relevant to candidates building a broader Red Hat certification path because EX380 counts toward earning Red Hat Certified Architect in OpenShift. That longer-term value should not replace a more immediate question: will the work represented by the exam match the responsibilities you want to perform?
The exam’s skills apply to self-managed OpenShift and managed services, including Red Hat OpenShift Service on AWS and Azure Red Hat OpenShift. The underlying administration experience is therefore useful across deployment models, although you should not assume that every provider-specific procedure is interchangeable.
Which skills should your preparation cover?
Prepare by capability rather than by memorizing product terms. The supplied official material identifies application deployment, Operators, GitOps with Jenkins, enterprise authentication, persistent storage, worker-node recovery, access control, and data protection as important areas. Build a lab sequence that makes you configure each capability, validate it, and repair it after an intentional fault.
Red Hat’s certification page lists deploying Kubernetes applications, managing Operators, implementing GitOps with Jenkins, configuring enterprise authentication, managing persistent storage, and recovering failed worker nodes among the credential’s capabilities. These topics connect: an application may depend on an Operator, persistent storage, identity mappings, and a recovery procedure at the same time.
EX380 objectives include backing up and restoring applications with OpenShift API for Data Protection. The scope includes application data, resources, images, and volume snapshots. Do not study backup as a single command. Practice identifying what must be protected, creating a recoverable state, restoring it into an appropriate target, and checking that the restored application actually works.
The objectives also include configuring role-based access control, authentication tokens, and authentication certificates with kubeconfig files. Your practice should distinguish user identity from authorization, then verify access using accounts or configuration files with deliberately different permissions. A configuration that works only because you used an administrator context has not demonstrated the required control.
Authentication work includes configuring OpenShift authentication and identities, integrating LDAP and OIDC with Red Hat SSO Keycloak, and managing multiple identity providers. Study the flow from identity-provider configuration to user identity, group membership, permissions, and login behavior. Keep a written record of prerequisites and rollback steps because authentication changes can affect administrative access.
Red Hat’s listed capabilities also include managing Operators and implementing GitOps with Jenkins. Practice the complete operating cycle: discover the required Operator or application definition, install or configure it appropriately, observe status and events, identify a failed reconciliation, and make a controlled change through the selected automation workflow. The objective is reliable administration, not merely producing a successful initial deployment.
Are official blueprint percentages available?
No verified blueprint percentages are supplied in the available research for this guide, so do not assign study time using invented domain weights. Use the official objectives and your own diagnostic results instead. If Red Hat publishes revised domain percentages, read each percentage together with its named exam domain before changing your plan.
A practical substitute is a skills matrix with one row for each objective area: deployment, Operators, GitOps with Jenkins, authentication and identities, RBAC and kubeconfig-based credentials, persistent storage, backup and restore, and worker-node recovery. Mark each row as explain, perform, troubleshoot, or repeat under pressure. The weakest operational rows deserve the earliest lab time.
Avoid comparing bare percentages from third-party pages or practice products. Even an accurate percentage can become misleading if it belongs to an older version or a differently named domain. Confirm the version and domain labels on Red Hat’s official EX380 material before treating any weighting as current.
How should you measure readiness before booking?
Book only after you can complete representative OpenShift administration tasks from a clean starting point and explain how you verified the result. A useful readiness check is not whether you recognize commands; it is whether you can choose an approach, apply it with least privilege, diagnose failure, and leave the environment in a demonstrably correct state.
Begin with a gap assessment against the official objectives. For every area, record whether you have performed the task recently, performed it only with a tutorial, or understand it only conceptually. “Tutorial-dependent” should count as a gap because performance-based assessment requires independent execution in a live system environment.
Use a fresh practice scenario for each checkpoint. For example, give yourself an application deployment requirement, an access restriction, a storage requirement, or a recovery problem without copying a prepared solution. Afterward, inspect resources, events, logs, status conditions, and user access. Write down the first symptom, the likely cause, the corrective action, and the verification evidence.
A candidate who can finish only when every command is remembered exactly may need more practice with documentation navigation and diagnostic reasoning. A candidate who can solve the task but cannot verify persistence, access boundaries, or recovery completeness should also delay booking. These checks are practical recommendations, not Red Hat pass criteria.
What practice environment should you build?
Use a version-aligned OpenShift environment in which you can safely change authentication, storage, Operators, automation, and worker-node conditions. The environment should support repeatable resets and observation of cluster behavior. If you cannot reproduce a failure, your study will tend to reward memorization instead of operational understanding.
Keep the lab deliberately small but connected. Create several namespaces or projects, at least two classes of user access, a stateful workload, an Operator-managed component, and an application deployment that can be handled through an automated workflow. The exact topology is a study choice; the important point is that each task produces evidence you can inspect.
Maintain a lab journal with four entries for every exercise: objective, implementation, verification, and recovery. Include the resource names, relevant status conditions, events, logs, and commands or documentation references that helped. This journal becomes a troubleshooting index and exposes weak verification habits before the exam.
Practice destructive operations only in an environment you can recreate. A worker-node failure exercise, identity-provider change, or restore operation should have a defined rollback or reset method. Never use production data or credentials for study experiments, and do not treat public exam dumps or leaked questions as a preparation method.
How should you practise troubleshooting?
Inject one fault at a time and start from symptoms rather than from a known answer. Examples include an unavailable application, an Operator that is not reaching the expected state, a denied request caused by permissions, a storage attachment problem, or a node that is not serving workloads. Record how you narrowed the fault before changing configuration.
Separate observation from intervention. First inspect status, events, logs, related resources, and recent changes. Then state a hypothesis, make the smallest reasonable correction, and verify the outcome. This discipline prevents random edits and gives you a repeatable method when a task combines several OpenShift components.
What study sequence works for most candidates?
Study in dependency order: establish OpenShift administration fundamentals, then add security and storage, followed by Operators and application automation, and finish with protection and recovery. This sequence lets you troubleshoot higher-level failures using a sound understanding of projects, resources, identities, scheduling, and persistent data.
First, confirm the foundation associated with DO180 and DO280 topics for OpenShift version 4.18 and later versions, which Red Hat identifies as the stated prerequisite knowledge. Review project and resource management, application deployment, configuration, networking concepts, storage behavior, cluster access, and routine diagnostics. Do not spend the first phase on isolated advanced features if basic administration is slow.
Next, practise authorization and authentication. Configure role-based access, work with tokens and certificate-based kubeconfig files, and test each identity against intended permissions. Then work through identity providers, LDAP, OIDC, Red Hat SSO Keycloak, and multiple-provider management. Make access verification part of every exercise rather than a final activity.
After that, combine application delivery with Operators and GitOps using Jenkins. Start with a small application, then introduce a managed component or operational dependency. Observe reconciliation and deployment behavior, identify where configuration lives, and practise correcting drift through a controlled workflow. The goal is to understand the relationship between desired state, automation, and cluster state.
Finish with persistent storage, OpenShift API for Data Protection, and worker-node recovery. Test both the normal path and a failure path. Restore data and resources, confirm images and volume snapshots where applicable, and check application behavior after recovery. For node work, focus on safe diagnosis and the effect on workloads rather than memorizing a single failure command.
A practical EX380 study roadmap
A flexible roadmap should have four stages: baseline assessment, focused configuration practice, integrated failure exercises, and final verification. Adjust the length of each stage to your experience instead of forcing an arbitrary calendar. Move forward when you can demonstrate the current stage without step-by-step assistance and can explain why your verification proves success.
Stage one: map the objectives to evidence
Create the skills matrix before opening practice questions or tutorials. For each objective, link to one lab exercise and one verification method. Identify the tasks you have never performed, the tasks you perform only in production with help from others, and the tasks that fail when the environment is unfamiliar. This produces a study backlog based on evidence.
Read the official EX380 page and note its version statement, audience, prerequisite guidance, and objectives. Use the Red Hat training and certification pages as the authority for scope. Treat community notes as optional explanations, not as proof that a topic is current or assessed.
Stage two: build repeatable configuration habits
Work through identity, RBAC, kubeconfig credentials, storage, Operators, application deployment, and Jenkins-based GitOps in separate lab sessions. At the end of each session, reset the environment and repeat the task from a short requirement rather than from your notes. If the second attempt is substantially faster and still verified, the skill is becoming operational.
Keep commands and manifests in a personal reference set, but annotate decisions rather than copying unexplained snippets. Note which values are environment-specific, which permissions are intentionally narrow, and which status or event confirms completion. This helps prevent a common mistake: applying a technically valid configuration that does not satisfy the stated operational requirement.
Stage three: combine objectives under failure
Create integrated exercises in which an application depends on identity, storage, an Operator, or an automated deployment path. Introduce one failure, diagnose it, repair it, and verify the entire service. Then repeat with a different fault. Integrated practice matters because enterprise administration rarely presents one isolated feature at a time.
Include a backup-and-restore exercise that covers resources, application data, images, and volume snapshots where the lab supports those elements. Afterwards, test the restored application from the perspective of a permitted user and inspect its data. A restore that completes technically but leaves access or application state unverified is incomplete practice.
Stage four: perform a final readiness rehearsal
Use unfamiliar task wording and a clean environment. Work without a prepared solution, keep a time-neutral record of obstacles, and review every result for correctness, security, and persistence. The rehearsal should reveal whether you lose time locating resources, diagnosing status, changing contexts, or validating recovery.
After the rehearsal, classify each problem as knowledge, command fluency, documentation search, or verification failure. Fix the underlying category with a targeted repetition. Do not respond to uncertainty by collecting more random questions; performance tasks require transferable administration ability, not recognition of remembered answer patterns.
What mistakes most often weaken preparation?
The most damaging preparation mistakes are treating EX380 as a multiple-choice theory test, practising only successful deployments, relying on administrator access, and ignoring recovery verification. Correct these habits by performing tasks independently, introducing faults, testing least privilege, and proving that data and services remain usable after changes.
Reading commands without using them creates false confidence. Replace passive review with a requirement-first exercise: state the desired result, implement it, inspect the cluster, and explain the evidence. When an exercise fails, resist immediately replacing the configuration with a copied answer. Find the failure signal and understand the correction.
Practising only with unrestricted permissions hides authorization errors. Use separate identities or kubeconfig files and test both allowed and denied actions. This is particularly important because EX380 objectives include RBAC, tokens, certificates, and kubeconfig-related authentication controls.
Another mistake is treating authentication, storage, and backup as isolated features. A user may be authenticated but unauthorized; a volume may exist but not contain the expected state; a backup may complete but not restore all required components. Build cross-checks into your lab so that each configuration is tested from the next dependent layer.
Avoid studying an old OpenShift version without checking the current official page. EX380 is based on OpenShift Container Platform 4.18 according to the supplied Red Hat source. Version drift can affect commands, resource behavior, interfaces, and documentation. Verify current objectives and platform information before your final preparation cycle.
Do not use dumps, leaked questions, or memorization claims as substitutes for practice. They cannot establish that you can perform live administrative work, and relying on them can direct study time toward material that is inaccurate, unauthorized, or unrelated to the current objectives.
What should you verify before scheduling?
Confirm the current exam information on Red Hat’s official EX380 page, then use the Red Hat scheduler to manage the booking through your Red Hat account. Check the available scheduling and delivery information shown for your location and account at the time of booking; the supplied sources do not establish universal dates, prices, durations, languages, or delivery options.
Red Hat provides an online scheduler for scheduling and managing certification exams through a Red Hat account. Make sure you can access the relevant account before you are ready to book. Resolve account, identity, or eligibility questions through Red Hat rather than relying on a third-party listing.
Do not assume that a course enrolment is the same as exam readiness. Red Hat identifies DO180 and DO280 version 4.18-and-later knowledge as corresponding to stated prerequisite topics, while also recommending current OpenShift Administration certification or equivalent skills. Compare your actual hands-on background with the objectives before choosing a training or exam date.
Check the credential-maintenance implications as part of your planning. Red Hat states that its certifications have three-year validity and may be maintained through flexible renewal paths. Confirm the current renewal rules in the official certification program guide because renewal routes and program details can change.
How should you use Red Hat courses and documentation?
Use official training as a structured way to close specific skill gaps, not as evidence that every objective is already mastered. The DO381 course is presented by Red Hat as OpenShift Administration III: Scaling Deployments in the Enterprise with Exam, so it may help candidates who need structured enterprise administration practice, but your final readiness decision should still come from objective-based lab performance.
Start with the EX380 objectives and map each course module or documentation topic to a concrete task. After learning a feature, perform it without the instructor’s sequence, introduce a controlled fault, and verify the result. This converts course exposure into evidence of independent ability.
Keep the official EX380 page, certification page, scheduler, and certification program guide as your primary reference points. Documentation searches should support your troubleshooting process, but do not assume that an unofficial command sequence is appropriate for the current OpenShift version or for the permissions available in a task.
What should you do next?
Your next action is to compare the official EX380 objectives with your recent OpenShift work and schedule a diagnostic lab, not to book immediately or collect more memorization material. Use the result to choose between foundation review, focused advanced practice, or an integrated readiness rehearsal.
If the foundation is weak, revisit the DO180 and DO280-aligned administration topics before concentrating on identity providers, GitOps, protection, and recovery. If fundamentals are solid, begin with the least familiar advanced area and connect it to an application or operational scenario. If every area is familiar, test yourself in a clean environment with deliberately incomplete information.
Before scheduling, confirm the current OpenShift version reference, prerequisite expectations, and account access on Red Hat’s official pages. Use the scheduler for the actual booking process and check location-specific details there. After passing, record the credential date and review the official program guidance so you can plan its three-year validity and available renewal paths.
Conclusion
EX380 preparation is strongest when it mirrors the work the credential represents: controlled configuration, least-privilege access, application operations, automation, data protection, and recovery. Build evidence through repeatable labs, diagnose failures instead of memorizing fixes, and verify every result from the user, workload, and data perspectives. When your objective matrix shows independent performance on the current OpenShift 4.18 scope, confirm live scheduling details with Red Hat and make the booking decision from demonstrated readiness.
