IT업종 종사자분들은 모두 승진이나 연봉인상을 위해 자격증을 취득하려고 최선을 다하고 계실것입니다. 하지만 쉴틈없는 야근에 시달려서 공부할 시간이 없어 스트레스가 많이 쌓였을것입니다. Pass4Test의RedHat인증 EX380덤프로RedHat인증 EX380시험공부를 해보세요. 시험문제커버율이 높아 덤프에 있는 문제만 조금의 시간의 들여 공부하신다면 누구나 쉽게 시험패스가능합니다.
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration (EX380) |
| Exam Number: | EX380 |
| Exam Price: | USD 400 (varies by region) |
| Passing Score: | Pass/Fail (performance-based scoring by Red Hat; exact numeric score not publicly disclosed) |
| Exam Duration: | 240 minutes |
| Real Exam Qty: | Performance-based exam (typically 1–3 hands-on tasks) |
| Exam Format: | Hands-on practical tasks in OpenShift and automation environments, Performance-based lab exam |
| Available Languages: | English |
| Certificate Validity Period: | 3 years |
| Related Certifications: | Red Hat Certified Engineer (RHCE) Red Hat Certified Specialist in OpenShift Administration Red Hat Certified System Administrator (RHCSA) |
| Recommended Training: | Red Hat Ansible Automation Platform training Red Hat OpenShift Administration courses |
| Exam Registration: | Red Hat Certification Catalog Red Hat Training and Exams |
| Sample Questions: | RedHat EX380 Sample Questions |
| Exam Way: | Online remote exam or onsite testing center (performance-based lab environment) |
| Pre Condition: | No strict prerequisites; RHCSA or equivalent experience with Linux, containers, OpenShift, and Ansible strongly recommended. |
| Official Syllabus URL: | https://www.redhat.com/en/services/certification |
Pass4Test의RedHat EX380 덤프 구매 후 등록된 사용자가 구매일로부터 일년 이내에RedHat EX380시험에 실패하셨다면 Pass4Test메일에 주문번호와 불합격성적표를 보내오셔서 환불신청하실수 있습니다.구매일자 이전에 발생한 시험불합격은 환불보상의 대상이 아닙니다. 개별 인증사는 불합격성적표를 발급하지 않기에 재시험신청내역을 환불증명으로 제출하시면 됩니다.
| 주제 | 소개 |
|---|---|
| 주제 1 |
|
| 주제 2 |
|
| 주제 3 |
|
| 주제 4 |
|
| 주제 5 |
|
질문 # 10
Create and use client certificates with kubeconfig (CSR flow)
Task Information : Generate a client key/CSR for audit2, approve it, extract the signed cert, and build a kubeconfig using that cert.
정답：
설명：
See the solution below in Explanation:
Explanation:
* Generate private key and CSR
* openssl genrsa -out audit2.key 2048
* openssl req -new -key audit2.key -out audit2.csr -subj "/CN=audit2/O=auditors"
* CN becomes username; O can map to groups in some setups.
* Base64 encode CSR for the API object
* CSR=$(base64 -w0 audit2.csr)
* Kubernetes CSR object expects base64-encoded request data.
* Create the CSR object
* cat < < EOF | oc apply -f -
* apiVersion: certificates.k8s.io/v1
* kind: CertificateSigningRequest
* metadata:
* name: audit2-csr
* spec:
* request: ${CSR}
* signerName: kubernetes.io/kube-apiserver-client
* usages:
* - client auth
* EOF
* Approve the CSR
* oc adm certificate approve audit2-csr
* Approval triggers certificate issuance.
* Extract the signed certificate
* oc get csr audit2-csr -o jsonpath='{.status.certificate}' | base64 -d > audit2.crt
* Produces the client certificate file.
* Build kubeconfig using cert/key
* oc config set-credentials audit2 \
* --client-certificate=audit2.crt --client-key=audit2.key \
* --embed-certs=true --kubeconfig=audit2.kubeconfig
* oc config set-cluster lab \
* --server="$(oc whoami --show-server)" \
* --insecure-skip-tls-verify=true \
* --kubeconfig=audit2.kubeconfig
* oc config set-context audit2 \
* --cluster=lab --user=audit2 --namespace=default \
* --kubeconfig=audit2.kubeconfig
* Creates a kubeconfig that authenticates using client certificates.
* Test
* oc --kubeconfig=audit2.kubeconfig get ns
질문 # 11
Configure and synchronize OpenShift groups from LDAP (group sync)
Task Information : Create an LDAP group-sync config, run a one-time sync, and confirm groups exist in OpenShift.
정답：
설명：
See the solution below in Explanation:
Explanation:
* Create a group sync config file (example groupsync.yaml)
* This file defines how OpenShift queries LDAP for groups and members.
* Run a one-time group sync
* oc adm groups sync --sync-config=groupsync.yaml --confirm
* --confirm actually applies changes (without it, it's a dry-run preview).
* Verify groups created/updated
* oc get groups
* oc describe group < groupname >
* Confirms group objects exist and membership is present.
질문 # 12
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.
정답：
설명：
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 >
질문 # 13
Prevent workloads from running on dedicated nodes (taints)
Task Information : Apply a taint to dedicated nodes so only pods with tolerations can run there.
정답：
설명：
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.
질문 # 14
Create and apply a MachineConfig (set MOTD on workers)
Task Information : Create a MachineConfig that writes /etc/motd on worker nodes.
정답：
설명：
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.
질문 # 15
......
EX380공부문제: https://www.pass4test.net/EX380.html