Free PDF Accurate RedHat - EX380 - Red Hat Certified Specialist in OpenShift Automation and Integration Exam Guide

The web-based EX380 practice test is accessible via any browser. This EX380 mock exam simulates the actual RedHat EX380 exam and does not require any software or plugins. Compatible with iOS, Mac, Android, and Windows operating systems, it provides all the features of the desktop-based EX380 Practice Exam software.

RedHat EX380 Exam Syllabus Topics:

TopicDetails
Topic 1
  • Configure and manage OpenShift Authentication and Identities: Covers integrating OpenShift with external identity providers like LDAP and Keycloak, managing RBAC, group synchronization, and kubeconfig-based authentication.
Topic 2
  • Manage workloads with cluster partitioning: Covers dedicating cluster nodes to specific workloads by configuring node pools, machine configurations, and special-purpose operators.
Topic 3
  • Manage cluster monitoring and metrics: Covers troubleshooting application and cluster performance issues and managing alerts and notifications.
Topic 4
  • Back up and restore applications with OpenShift API for Data Protection (OADP): Covers deploying OADP, performing full application backups including data and resources, using volume snapshots, and scheduling and restoring backups.
Topic 5
  • Provision and inspect cluster logging: Covers deploying and configuring OpenShift logging with Vector and Loki, forwarding logs externally, querying logs, and diagnosing logging issues.

>> EX380 Exam Guide <<

Another way to prepare for the EX380 Exam

The EX380 dumps of TestKingIT include valid EX380 questions PDF and customizable Red Hat Certified Specialist in OpenShift Automation and Integration (EX380) practice tests. Our 24/7 customer support provides assistance to help EX380 Dumps users solve their technical hitches during their test preparation. The EX380 exam questions of TestKingIT come with up to 365 days of free updates and a free demo.

RedHat Red Hat Certified Specialist in OpenShift Automation and Integration Sample Questions (Q21-Q26):

NEW QUESTION # 21
Export and import a Kubernetes application (YAML export)
Task Information : Export typical app objects from orders and apply them into a new namespace orders- copy.

Answer:

Explanation:
See the solution below in Explanation:
Explanation:
* Export objects to YAML
* oc -n orders get deploy,svc,route,cm,secret -o yaml > orders-app.yaml
* Exports key application resources.
* Create target namespace
* oc new-project orders-copy
* Apply exported YAML
* oc -n orders-copy apply -f orders-app.yaml
* Recreates resources (some fields may need adjustment, like namespaces or immutable fields).
* Validate
* oc -n orders-copy get all


NEW QUESTION # 22
Recover a NotReady worker node (basic remediation workflow)
Task Information : Diagnose a NotReady worker node and restore it to Ready state using standard OpenShift admin workflow.

Answer:

Explanation:
See the solution below in Explanation:
Explanation:
* Identify failing node and status
* oc get nodes
* Confirms which node is NotReady.
* Inspect node conditions and events
* oc describe node < worker >
* Shows kubelet condition issues (network, disk pressure, runtime, etc.).
* Check MachineConfigPool state
* oc get mcp
* oc describe mcp worker
* If MCP is degraded, node may be stuck applying a config.
* Check node logs (kubelet)
* oc adm node-logs < worker > --path=kubelet.log
* Often reveals why node isn't reporting Ready.
* Remediate based on symptom
* Examples:
* If out of disk: free space, then verify kubelet recovers.
* If stuck MCO: investigate current/desired config and fix broken MachineConfig.
* If node cordoned/drained incorrectly: uncordon after remediation.
* oc adm uncordon < worker >
* Confirm node returns Ready
* oc get node < worker >


NEW QUESTION # 23
Configure log forwarding to an external endpoint
Task Information : Configure Cluster Logging to forward application logs to an external output using ClusterLogForwarder.

Answer:

Explanation:
See the solution below in Explanation:
Explanation:
* Verify logging namespace and resources
* oc get ns openshift-logging
* oc -n openshift-logging get clusterlogforwarder
* ClusterLogForwarder configures pipelines and outputs.
* Create/Edit ClusterLogForwarder (example structure)
* Define an output (external system) and pipeline selecting application logs.
* Apply via YAML:
* oc -n openshift-logging apply -f clusterlogforwarder.yaml
* Validate collector pods are healthy
* oc -n openshift-logging get pods
* Forwarding relies on collectors (vector/fluentd depending config).
* Generate a test log line
* oc -n openshift-logging run logger --image=busybox --restart=Never -- /bin/sh -c 'echo hello- forwarding; sleep 5'
* This creates a known message to search in the external endpoint.
* Confirm logs arrive at destination
* Use your external system's query/search to confirm hello-forwarding.


NEW QUESTION # 24
Service Accounts and RBAC - Grant Cluster Reader Role

Answer:

Explanation:
See the solution below in Explanation:
Explanation:
Step 1: Confirm the service account exists in auth-audit.
It must exist before a role can be assigned to it.
Step 2: Run the command:
oc adm policy add-cluster-role-to-user cluster-reader system:serviceaccount:auth-audit:audit Step 3: Verify the binding is added.
The lab output shows:
clusterrole.rbac.authorization.k8s.io/cluster-reader added: "system:serviceaccount:auth-audit:audit" Detailed explanation:
This binds the cluster-reader cluster role to the audit service account. The full subject format system:
serviceaccount:namespace:name is required because OpenShift RBAC needs the exact service account identity. The cluster-reader role is broader than a project-scoped view role because it allows read-level access across cluster resources. This is appropriate for auditing or inspection use cases where the account must observe but not modify. The distinction between cluster roles and namespaced roles is important: cluster roles apply to non-namespaced resources and broad cluster visibility, while local roles are limited to individual projects. This Task is a classic RBAC operation that combines identity creation with controlled privilege assignment.


NEW QUESTION # 25
Add tolerations to a deployment
Task Information : Update payments/api deployment to tolerate dedicated=payments:NoSchedule.

Answer:

Explanation:
See the solution below in Explanation:
Explanation:
* Patch deployment with toleration
* oc -n payments patch deploy api --type=merge -p '{
* "spec":{"template":{"spec":{"tolerations":[
* {"key":"dedicated","operator":"Equal","value":"payments","effect":"NoSchedule"}
* ]}}}
* }'
* Toleration allows pods to schedule onto tainted nodes.
* Verify scheduling
* oc -n payments get pods -o wide


NEW QUESTION # 26
......

TestKingIT has been going through all ups and downs tested by the market, and now our EX380 exam questions have become perfectly professional. We never circumvent the difficulties of our EX380 study materials happened on the road as long as there is bright at the end, and it is the satisfactory results you want. And we have helped so many of our customers achieve their certifications according to our EX380 learning guide.

Reliable EX380 Cram Materials: https://www.testkingit.com/RedHat/latest-EX380-exam-dumps.html