EX380 Exam Guide
This EX380 exam focuses on practical knowledge and real-world application scenarios related to the subject area. It evaluates your ability to understand core concepts, apply best practices, and make informed decisions in realistic situations rather than relying solely on memorization.
This page provides a structured exam guide, including exam focus areas, skills measured, preparation recommendations, and practice questions with explanations to support effective learning.
Exam Overview
The EX380 exam typically emphasizes how concepts are used in professional environments, testing both theoretical understanding and practical problem-solving skills.
Skills Measured
- Understanding of core concepts and terminology
- Ability to apply knowledge to practical scenarios
- Analysis and evaluation of solution options
- Identification of best practices and common use cases
Preparation Tips
Successful candidates combine conceptual understanding with hands-on practice. Reviewing measured skills and working through scenario-based questions is strongly recommended.
Practice Questions for EX380 Exam
The following practice questions are designed to reinforce key EX380 exam concepts and reflect common scenario-based decision points tested in the certification.
Question#1
SIMULATION
Task SIMULATION 10
Kubeconfig Management C Set Context in Kubeconfig
A. 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.
Question#4
1.SIMULATION
Task SIMULATION 1
Node Management C Remove Taint on Worker Node
A. Step 1: Log in to the OpenShift web console with an account that has sufficient cluster administrative privileges.
This Task is performed from the GUI, not the CLI. The lab hint explicitly places this under the worker node details page in the console.
Step 2: Navigate to Compute.
This area contains node-level resources, including control plane and worker nodes.
Step 3: Open Nodes.
Here you can view all nodes currently registered in the cluster.
Step 4: Select the required worker node.
Choose the exact worker node referenced by the lab Task SIMULATION.
Step 5: Open the Details tab.
The taint configuration is managed from the selected node’s details view.
Step 6: Locate the Taints section and click Edit.
A taint is used to control pod scheduling. If a worker has a taint, pods without matching tolerations may not schedule there.
Step 7: Remove the unwanted taint entry.
Removing the taint makes the worker eligible again for normal scheduling behavior, depending on the rest of the cluster policy.
Step 8: Click Save.
This commits the change so the node is updated and the scheduler can evaluate it without that taint.
Disclaimer
This page is for educational and exam preparation reference only. It is not affiliated with Red Hat, Red Hat Certified Specialist in OpenShift Automation and Integration, or the official exam provider. Candidates should refer to official documentation and training for authoritative information.
