We have considered that your time may be very tight, and you can only use some fragmented time to learn. Therefore, it is really important to be able to read our EX380 study materials anytime, anywhere. So we have developed our EX380 exam questions to three different versions: the PDF, Software and APP online. They have covered all conditions that you will be in to study on our EX380 learning guide. For example, the time you want to study on phone, computer, laptop, paper and so on.
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration |
| Exam Number: | EX380 |
| Related Certifications: | Red Hat Certified Engineer (RHCE) Red Hat Certified Architect (RHCA) |
| Exam Duration: | 180 minutes |
| Exam Format: | Hands-on labs, Performance-based |
| Real Exam Qty: | 15 |
| Certificate Validity Period: | 3 years |
| Exam Price: | $400 USD |
| Available Languages: | Japanese, English, Chinese (Simplified) |
| Passing Score: | 210 (on a scale of 100-300) |
| Sample Questions: | RedHat EX380 Sample Questions |
| Exam Way: | On-site at Red Hat certified testing centers or online proctored exam |
| Pre Condition: | Red Hat recommends taking the DO180 (Red Hat OpenShift Administration I) course or having equivalent knowledge before attempting this exam. Familiarity with Linux administration is strongly recommended. |
| Official Syllabus URL: | https://www.redhat.com/en/services/training/ex380-red-hat-certified-specialist-openshift-automation-and-integration-exam |
These EX380 exam question formats contain real, valid, and updated RedHat EX380 exam questions that will assist you in RedHat Red Hat Certified Specialist in OpenShift Automation and Integration exam preparation and enable you to pass the challenging RedHat EX380 Exam with good scores. The RedHat EX380 questions are prepared by highly experienced professionals and, thus, are kept to the point and concise.
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 22
Kubeconfig Management - Set Context in Kubeconfig
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
Step 1: Verify the cluster name, namespace, and user name that should be referenced.
The lab uses cluster api-ocp4-example-com:6443, namespace audit-ns, and user audit-sa.
Step 2: Run the command:
oc config set-context audit --cluster api-ocp4-example-com:6443 --namespace audit-ns --user audit-sa -- kubeconfig audit.config Step 3: Confirm context creation.
The lab output shows:
Context "audit" created.
Detailed explanation:
A kubeconfig context ties together three things: a cluster endpoint, a user identity, and optionally a default namespace. This Task creates a context named audit in the file audit.config. Contexts are useful because they simplify repeated administration by letting the user switch between prepared working environments instead of re-entering cluster and namespace details each time. The namespace portion is especially helpful for project- scoped operations, because commands run under that context default to the chosen namespace. Accuracy matters here: if the user name in the context does not match the credentials entry or the cluster name does not exist in the kubeconfig, the context will not function as intended.
NEW QUESTION # 23
Restore application into same namespace
Task Information : Restore from backup orders-full and validate the app resources return.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Start the restore
* velero restore create orders-restore --from-backup orders-full
* Monitor restore status
* velero restore get
* velero restore describe orders-restore --details
* Validate restored resources
* oc -n orders get all
* oc -n orders get pvc
* Ensure deployments/pods/services and PVCs exist and pods become Running.
NEW QUESTION # 24
Backup and Restore - Restore Application from Existing Backup
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
Step 1: Make sure Velero is installed and configured in the environment.
The Task SIMULATION assumes an existing backup named backup-app-daily is already present.
Step 2: Run the restore command:
velero restore create --from-backup backup-app-daily
Step 3: Confirm the restore request is submitted.
The lab output shows:
Restore request "backup-app-daily-2024" submitted successfully.
Detailed explanation:
This command instructs Velero to create a restore operation using the existing backup called backup-app- daily. Velero is commonly used to protect Kubernetes and OpenShift resources by backing up object definitions and, when configured, persistent data integrations. The command does not manually recreate resources one by one; instead, it leverages the metadata captured during backup. A successful restore submission means the request has been accepted, not necessarily that every object has already been fully restored. In practical administration, you would often follow this by checking restore status and validating the application namespace, pods, services, routes, and storage bindings. This lab Task SIMULATION focuses specifically on initiating the restore from the named backup source.
NEW QUESTION # 25
Dedicate nodes to a workload using labels and nodeSelector
Task Information : Label two nodes with workload=payments and schedule a deployment only onto those nodes.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Label the chosen worker nodes
* oc label node worker-1 workload=payments
* oc label node worker-2 workload=payments
* Node labels are key/value metadata used by the scheduler.
* Add a nodeSelector to the deployment
* oc -n payments patch deploy api --type=merge -p '{
* "spec":{"template":{"spec":{"nodeSelector":{"workload":"payments"}}}}
* }'
* Forces pods to schedule only to nodes that match the label.
* Verify placement
* oc -n payments get pods -o wide
* Confirms pods are running on the intended nodes.
NEW QUESTION # 26
Prevent workloads from running on dedicated nodes (taints)
Task Information : Apply a taint to dedicated nodes so only pods with tolerations can run there.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Taint nodes
* oc adm taint nodes worker-1 dedicated=payments:NoSchedule
* oc adm taint nodes worker-2 dedicated=payments:NoSchedule
* NoSchedule blocks new pods that do not tolerate the taint.
* Confirm taints
* oc describe node worker-1 | grep -i taints -A2
* Ensures taints are present.
* Validate effect
* A normal deployment without tolerations will remain Pending if it can only land on those tainted nodes.
NEW QUESTION # 27
......
PDF EX380 VCE: https://www.trainingdump.com/RedHat/EX380-practice-exam-dumps.html