We have free demo of our EX380 exam questions offering the latest catalogue and brief contents for your information on the website, if you do not have thorough understanding of our EX380 study materials. Many exam candidates build long-term relation with our company on the basis of our high quality EX380 Guide engine. And our EX380 training braindumps have became their best assistant on the way to pass the exam.
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration |
| Exam Number: | EX380 |
| Exam Format: | Hands-on labs, Performance-based |
| Certificate Validity Period: | 3 years |
| Available Languages: | English, Chinese (Simplified), Japanese |
| Exam Price: | $400 USD |
| Exam Duration: | 180 minutes |
| Real Exam Qty: | 15 |
| Related Certifications: | Red Hat Certified Architect (RHCA) Red Hat Certified Engineer (RHCE) |
| 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 |
The money you have invested on updating yourself is worthwhile. The knowledge you have learned is priceless. You can obtain many useful skills on our EX380 study guide, which is of great significance in your daily work. Never feel sorry to invest yourself. Our EX380 Exam Materials deserve your choice. If you still cannot make decisions, you can try our free demo of the EX380 training quiz.
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 24
Configure project-wide default tolerations
Task Information : Configure the payments namespace so new pods automatically include a default toleration.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Annotate the namespace with default tolerations
* oc annotate ns payments \
* scheduler.alpha.kubernetes.io/defaultTolerations='[{"key":"dedicated","operator":"Equal","value":" payments","effect":"NoSchedule"}]' \
* --overwrite
* Some clusters honor this pattern; if not, the fallback is mutating admission or editing workloads.
* Create a new pod/deployment in the namespace
* Then verify its spec includes tolerations:
* oc -n payments get pod < pod > -o yaml | grep -n tolerations -A5
NEW QUESTION # 25
Create an Argo CD Application (OpenShift GitOps)
Task Information : Create an Argo CD Application that syncs from Git into namespace gitops-demo with automated sync enabled.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Create target namespace
* oc new-project gitops-demo
* Destination must exist (unless Argo is configured to auto-create).
* Create Application manifest
* apiVersion: argoproj.io/v1alpha1
* kind: Application
* metadata:
* name: demo-app
* namespace: openshift-gitops
* spec:
* project: default
* source:
* repoURL: https://git.example.com/org/repo.git
* targetRevision: main
* path: manifests/demo
* destination:
* server: https://kubernetes.default.svc
* namespace: gitops-demo
* syncPolicy:
* automated:
* prune: true
* selfHeal: true
* automated: enables auto sync.
* prune: removes deleted objects from Git.
* selfHeal: corrects drift.
* Apply Application
* oc apply -f demo-app.yaml
* Verify sync health
* oc -n openshift-gitops get application demo-app -o yaml | grep -i -E "sync|health" -n
* oc -n gitops-demo get all
NEW QUESTION # 26
Kubeconfig Management - Use Context
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
Step 1: Make sure the context already exists in the kubeconfig file.
This follows the context creation Task SIMULATION .
Step 2: Run the command:
oc config use-context audit --kubeconfig audit.config
Step 3: Confirm the active context switches successfully.
The lab output shows:
Switched to context "audit".
Detailed explanation:
This command activates the audit context inside the specified kubeconfig file. Once selected, subsequent oc commands using that kubeconfig will default to the cluster, user, and namespace associated with that context.
This is operationally important because many administration mistakes come from running commands against the wrong cluster or project. Using explicit context switching reduces that risk and makes the kubeconfig usable for the intended audit workflow. In exams and real environments alike, the context is what turns separate kubeconfig elements into a working session configuration. Without switching to the correct context, even a well-formed kubeconfig may not be used as expected.
NEW QUESTION # 27
Configure RBAC roles with users and groups
Task Information : Grant edit to group dev-team in namespace payments, and grant view to user auditor1.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Create (or switch to) the project
* oc new-project payments
* Namespace must exist before applying rolebindings.
* Grant edit to the group
* oc -n payments policy add-role-to-group edit dev-team
* Members of dev-team can modify most resources in payments.
* Grant view to a user
* oc -n payments policy add-role-to-user view auditor1
* auditor1 can read resources but not change them.
* Verify rolebindings
* oc -n payments get rolebinding
NEW QUESTION # 28
Export and import container images (mirror to internal registry)
Task Information : Pull an image from an external registry, push it into the OpenShift internal registry, and update a deployment to use the mirrored image.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Log in to OpenShift internal registry
* oc registry login
* Allows podman to push to the internal registry.
* Pull external image
* podman pull docker.io/library/nginx:1.25
* Gets the image locally.
* Tag for internal registry destination
* podman tag nginx:1.25 image-registry.openshift-image-registry.svc:5000/orders/nginx:1.25
* Uses the cluster service DNS name (works inside cluster network).
* Push to internal registry
* podman push image-registry.openshift-image-registry.svc:5000/orders/nginx:1.25
* Update deployment to use internal image
* oc -n orders set image deploy/web web=image-registry.openshift-image-registry.svc:5000/orders/nginx:
1.25
* Verify rollout
* oc -n orders rollout status deploy/web
* oc -n orders get pods -o wide
NEW QUESTION # 29
......
EX380 Reliable Dumps: https://www.validdumps.top/EX380-exam-torrent.html