We have been developing our EX380 practice engine for many years. We have no doubt about our quality of the EX380 exam braindumps. Our experience is definitely what you need. And especially our professional experts have been devoting in this field for over ten years. I believe no one can know the EX380 training guide than them. To combine many factors, EX380 real exam must be your best choice.
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration exam |
| Exam Number: | EX380 |
| Real Exam Qty: | Performance-based tasks, no fixed number |
| Related Certifications: | Red Hat Certified Architect (RHCA) |
| Certificate Validity Period: | 3 years |
| Exam Duration: | 240 minutes |
| Passing Score: | Not disclosed |
| Exam Price: | $450 USD / โฌ450 EUR |
| Available Languages: | English |
| Exam Format: | Performance-based, Practical tasks, Hands-on lab |
| Recommended Training: | DO380 - Red Hat OpenShift Automation and Integration |
| Exam Registration: | Red Hat Certification Portal |
| Sample Questions: | RedHat EX380 Sample Questions |
| Exam Way: | Online proctored or onsite at authorized test centers |
| Pre Condition: | Current Red Hat Certified Specialist in OpenShift Administration certification, or equivalent experience matching DO180 and DO280 course topics |
| Official Syllabus URL: | https://www.redhat.com/en/services/training/ex380-certified-specialist-openshift-automation-exam |
With the aim of helping aspirants to achieve the Red Hat Certified Specialist in OpenShift Automation and Integration (EX380) certification, Actual4dump is committed to providing the best quality and updated RedHat EX380 exam dumps. With their authentic and Real EX380 Exam Questions, you can be confident of passing the RedHat EX380 certification exam on the first try.
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
NEW QUESTION # 37
Resolve group synchronization conflicts (prune stale data)
Task Information : Run group sync with pruning to remove stale OpenShift group memberships that no longer exist in LDAP.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Run group sync with prune controls
* oc adm groups sync --sync-config=groupsync.yaml --confirm --prune-whitelist=/tmp/whitelist.txt
* Prune removes stale memberships/groups, but whitelist protects selected groups from pruning.
* Verify group membership reflects LDAP
* oc describe group < groupname >
* Confirms removed users are no longer listed.
NEW QUESTION # 38
Logging Configuration - Configure ClusterLogging in Web Console
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
Step 1: Log in to the OpenShift web console.
This Task is explicitly defined as a GUI workflow.
Step 2: Navigate to Operators .
Installed logging components are managed through the operator framework.
Step 3: Open Installed Operators .
This lists operators already deployed in the cluster.
Step 4: Select Red Hat OpenShift Logging .
This operator manages the cluster logging stack and its custom resources.
Step 5: Open the ClusterLogging instance.
The Task SIMULATION refers to editing the existing ClusterLogging custom resource.
Step 6: Switch to YAML View .
This allows direct editing of the logging custom resource specification.
Step 7: Edit the collection type and set it to vector.
This changes the log collector implementation.
Step 8: Click Save .
The operator will reconcile the resource and apply the updated collector configuration.
Detailed explanation:
The ClusterLogging custom resource controls the logging stack behavior in OpenShift. Changing the collection type to vector updates which collector technology is used for gathering node and container logs. In operator-managed platforms, direct YAML edits to the custom resource are the preferred method for changing managed behavior because the operator then applies and maintains the desired state. This Task tests both navigation skills in the web console and knowledge of where logging behavior is configured. Saving the resource triggers reconciliation, which is a core OpenShift operator pattern: the declared configuration is read and enforced by the operator rather than by manual per-pod changes.
NEW QUESTION # 39
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 # 40
Create and apply a MachineConfig (set MOTD on workers)
Task Information : Create a MachineConfig that writes /etc/motd on worker nodes.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Create the MachineConfig YAML (example content encoded in base64)
* apiVersion: machineconfiguration.openshift.io/v1
* kind: MachineConfig
* metadata:
* name: 99-worker-motd
* labels:
* machineconfiguration.openshift.io/role: worker
* spec:
* config:
* ignition:
* version: 3.2.0
* storage:
* files:
* - path: /etc/motd
* mode: 0644
* contents:
* source: data:text/plain;charset=utf-8;base64,VGhpcyBpcyBhIHdvcmtlciBub2RlLg==
* MachineConfig uses Ignition format; file content is typically base64.
* Apply it
* oc apply -f 99-worker-motd.yaml
* Watch worker MachineConfigPool roll out
* oc get mcp worker
* MCP will show Updating then Updated.
* Validate on a worker node (if you have node access)
* Confirm /etc/motd contains the expected text.
NEW QUESTION # 41
GitOps and MachineConfig - Trigger Argo CD Synchronization by Repository Update
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
Step 1: Confirm that the repository being pushed to is the same repository watched by the GitOps/Argo CD application.
This linkage is essential because GitOps acts only on configured source repositories and paths.
Step 2: Commit the MachineConfig changes.
The lab uses:
git commit -am "Add MachineConfig for motd"
Step 3: Push the changes to the tracked branch.
The lab uses:
git push origin main
Step 4: Allow Argo CD to detect the repository change and begin synchronization.
In a standard GitOps model, the controller compares the Git repository to the cluster state and applies drift correction or new desired resources.
Detailed explanation:
This sub Task SIMULATION is the operational purpose behind the previous Git command Task SIMULATION . The point is not merely to store a file in Git; it is to update the declarative source that Argo CD uses to reconcile the cluster. Once the repository is updated, Argo CD detects the new commit and syncs the MachineConfig into the cluster according to its application definition. This demonstrates a core automation principle in OpenShift GitOps: administrators do not treat the cluster as the primary editable surface. Instead, they modify Git and let the automation layer enforce state. That provides traceability, peer review potential, rollback capability, and consistency across environments.
NEW QUESTION # 42
......
EX380 Exam Overview: https://www.actual4dump.com/RedHat/EX380-actualtests-dumps.html