
EX380 is Red Hat's advanced hands-on OpenShift exam. Passing it earns the Red Hat Certified Advanced System Administrator in OpenShift credential, and the exam was earlier listed as the OpenShift Automation and Integration specialist exam. It goes beyond EX280 into enterprise identity (LDAP and Keycloak), OADP backups, cluster partitioning with machine configs, advanced scheduling, OpenShift GitOps with Argo CD, monitoring and logging with Vector and Loki. Senior OpenShift administrators and SREs at banks, telecom operators and GCCs in Hyderabad do this work every day.
This guide follows Red Hat's official EX380 exam page. It covers the exam facts, all seven objective areas, the commands and manifests to practise, a 6-week plan and 15 original practice tasks.
Quick facts (Red Hat, November 2026)
| Item | Detail |
|---|---|
| Exam | EX380 |
| Credential | Red Hat Certified Advanced System Administrator in OpenShift |
| Format | Performance-based: real tasks on a live cluster |
| Duration | 4 hours |
| Product version | Red Hat OpenShift Container Platform 4.22 |
| Documentation | Product documentation is available during the exam |
| Recommended preparation | DO280 and DO380, or similar experience as an advanced OpenShift administrator |
| Results | Total score by email from Red Hat, usually within 3 US business days |
Read the official EX380 exam page. Red Hat says more than one version of this exam is in use. Check the objectives for your assigned version in the Red Hat learning system before you book.
Exam objectives (summarised)
| Area | What it covers |
|---|---|
| Authentication and identities | LDAP and Red Hat SSO (Keycloak) OIDC; several identity providers; group sync, sync conflicts and scheduled sync; RBAC; tokens and certificates in kubeconfig files |
| Backup and restore with OADP | Export and import applications and images; deploy OADP; full backups of data and resources; volume snapshots; scheduled backups and restores |
| Cluster partitioning | Dedicated nodes for a workload; node pools; machine configurations; the Machine Config Operator and special-purpose operators |
| Pod scheduling | Dedicated nodes; taints, tolerations, labels and selectors; project tolerations; pod disruption budgets; affinity rules |
| OpenShift GitOps | Deploy the GitOps operator; users, instances and integrations; Argo CD; pipelines and repositories; Git, Helm and Kustomize; GitOps for cluster administration and applications |
| Cluster monitoring and metrics | Troubleshoot performance and availability; configure and silence alerts and notifications |
| Cluster logging | Forward logs to an external aggregator; short-term retention; Vector and Loki; Event Router; querying cluster and node logs; diagnosing logging problems |
Commands and manifests to practise
# LDAP group sync, then schedule it as a CronJob
oc adm groups sync --sync-config=ldap-sync.yaml --confirm
oc adm groups prune --sync-config=ldap-sync.yaml --confirm
# kubeconfig with a service account token
oc create token automation-sa --duration=24h -n ops
oc config set-credentials automation --token=<token> --kubeconfig=auto.kubeconfig
# dedicated infra nodes
oc label node worker-3 node-role.kubernetes.io/infra=
oc adm taint node worker-3 node-role.kubernetes.io/infra=reserved:NoSchedule
oc get mcp; oc get mc | tail
# project-wide node selector
oc annotate ns reports openshift.io/node-selector='node-role.kubernetes.io/infra='
A custom MachineConfigPool for infra nodes:
apiVersion: machineconfiguration.openshift.io/v1
kind: MachineConfigPool
metadata:
name: infra
spec:
machineConfigSelector:
matchExpressions:
- {key: machineconfiguration.openshift.io/role, operator: In, values: [worker, infra]}
nodeSelector:
matchLabels:
node-role.kubernetes.io/infra: ""
A pod disruption budget and a nightly OADP schedule:
apiVersion: policy/v1
kind: PodDisruptionBudget
metadata: {name: web-pdb, namespace: shop}
spec:
minAvailable: 2
selector:
matchLabels: {app: web}
---
apiVersion: velero.io/v1
kind: Schedule
metadata: {name: shop-nightly, namespace: openshift-adp}
spec:
schedule: "0 1 * * *"
template:
includedNamespaces: [shop]
ttl: 168h0m0s
An Argo CD Application that keeps a namespace in sync with Git:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata: {name: shop, namespace: openshift-gitops}
spec:
project: default
source:
repoURL: https://git.example.com/platform/shop.git
path: overlays/prod
targetRevision: main
destination: {server: https://kubernetes.default.svc, namespace: shop}
syncPolicy:
automated: {prune: true, selfHeal: true}
API versions for logging and OADP resources change between operator releases. In the exam, confirm them with oc explain and the documentation provided.
6-week study plan
| Week | Focus | Lab (an OpenShift 4.x cluster with cluster-admin) |
|---|---|---|
| 1 | LDAP and Keycloak identity providers, group sync and scheduling, RBAC, kubeconfig tokens and certificates | Sync an LDAP group nightly and give it edit on one project |
| 2 | OADP: install, backup storage, full backups, volume snapshots, schedules, restores | Delete a namespace and restore it from backup |
| 3 | Node labels, MachineConfigPools, machine configs, the Machine Config Operator | Create an infra pool and move a workload onto it |
| 4 | Taints, tolerations, project node selectors and tolerations, PDBs, affinity and anti-affinity | Drain a node without breaking a PDB-protected app |
| 5 | OpenShift GitOps: operator, Argo CD instances, RBAC, Helm and Kustomize sources, cluster configuration from Git | Manage a namespace, quota and RBAC from Git |
| 6 | Monitoring, alerts and silences; logging with Vector, Loki, the Event Router and log forwarding; timed practice | Forward application logs to an external syslog server; book the exam |
15 practice tasks with solutions
These are original tasks written for this guide, not exam questions.
1. Add LDAP login alongside existing HTPasswd users.
Add an LDAP identity provider to oauth/cluster, with its bind password in a secret in openshift-config.
2. Sync LDAP groups into OpenShift.oc adm groups sync --sync-config=<file> --confirm.
3. Keep groups in sync automatically.
Run the sync from a CronJob with a service account that is allowed to manage groups.
4. Remove OpenShift groups whose LDAP groups were deleted.oc adm groups prune --sync-config=<file> --confirm.
5. Give a script access to the cluster without a user password.
Create a service account, give it a role, generate a token and write it into a kubeconfig file.
6. Which operator backs up applications and persistent volumes?
OADP, which is based on Velero.
7. Back up a namespace every night and keep backups for a week.
Create a Velero Schedule with a cron expression and ttl: 168h.
8. How do you apply a configuration file only to infra nodes?
Create a MachineConfigPool that selects infra nodes and a MachineConfig with the infra role label.
9. Make every pod in a project run on infra nodes.
Set the openshift.io/node-selector annotation on the namespace.
10. Infra nodes are tainted. How do the project's pods still run there?
Give them matching tolerations, or set default tolerations for the project.
11. Stop a drain from taking down every replica of an app.
Create a PodDisruptionBudget with minAvailable or maxUnavailable.
12. Spread an app's replicas across nodes.
Use pod anti-affinity on the hostname topology key.
13. Make Argo CD undo manual changes in the cluster.
Set syncPolicy.automated.selfHeal: true on the Application.
14. Stop a known alert notifying during maintenance.
Create a silence for it in the console's alerting view (Alertmanager).
15. Record Kubernetes events in the logging stack.
Deploy the Event Router, which writes events to its log so the collector picks them up.
Before and after EX380
- Pass EX280 first; add VMs with EX316.
- Compare with CKA, and with GitOps in CGOA and CAPA.
- Learn it hands-on in our Kubernetes course and DevOps course; see live OpenShift and SRE jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches Kubernetes, OpenShift basics, GitOps and DevOps with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is EX380?
Red Hat's advanced hands-on OpenShift exam; passing it earns the Red Hat Certified Advanced System Administrator in OpenShift credential.
How long is EX380 and what format is it?
4 hours, performance-based, with real tasks on a live cluster.
Which OpenShift version is EX380 based on?
Red Hat OpenShift Container Platform 4.22. Red Hat says more than one exam version is in use, so check your assigned version's objectives.
Which courses prepare for EX380?
DO280 and DO380, or similar experience as an advanced OpenShift administrator.
Can I use documentation during EX380?
Yes. Product documentation is provided during the exam.
What does EX380 cover that EX280 doesn't?
LDAP and Keycloak identity, OADP backups, machine configs, advanced scheduling, OpenShift GitOps, monitoring and logging.



