안심하시고ITDumpsKR 를 선택하게 하기 위하여, ITDumpsKR에서는 이미RedHat EX380인증시험의 일부 문제와 답을 사이트에 올려놨으니 체험해보실 수 있습니다. 그러면 저희한테 신뢰가 갈 것이며 또 망설임 없이 선택하게 될 것입니다. 저희 덤프로 여러분은 한번에 시험을 패스할 수 있으며 또 개인시간도 절약하고 무엇보다도 금전상으로 절약이 제일 크다고 봅니다. ITDumpsKR는 여러분들한테 최고의RedHat EX380문제와 답을 제공함으로 100%로의 보장 도를 자랑합니다, 여러분은RedHat EX380인증시험의 패스로 IT업계여서도 또 직장에서도 한층 업그레이드되실 수 있습니다. 여러분의 미래는 더욱더 아름다울 것입니다.
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration exam |
| Exam Number: | EX380 |
| Exam Format: | Performance-based, Practical tasks, Hands-on lab |
| Available Languages: | English |
| Exam Duration: | 240 minutes |
| Real Exam Qty: | Performance-based tasks, no fixed number |
| Certificate Validity Period: | 3 years |
| Exam Price: | $450 USD / €450 EUR |
| Passing Score: | Not disclosed |
| Related Certifications: | Red Hat Certified Architect (RHCA) |
| 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 |
우리ITDumpsKR에는 아주 엘리트 한 전문가들로 구성된 팀입니다 그들은 끈임 없는 연구와 자기자신만의 지식으로 많은 IT관연 덤프자료를 만들어 냄으로 여러분의 꿈을 이루어드립니다, 기존의 시험문제와 답과 시험문제분석 등입니다. ITDumpsKR에서 제공하는RedHat EX380시험자료의 문제와 답은 실제시험의 문제와 답과 아주 비슷합니다. ITDumpsKR덤프들은 모두 보장하는 덤프들이며 여러분은 과감히 ITDumpsKR의 덤프를 장바구니에 넣으세요. ITDumpsKR에서 여러분의 꿈을 이루어 드립니다.
| 주제 | 소개 |
|---|---|
| 주제 1 |
|
| 주제 2 |
|
| 주제 3 |
|
| 주제 4 |
|
질문 # 16
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.
정답：
설명：
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.
질문 # 17
Install OADP Operator and verify Velero components
Task Information : Install the OADP operator and confirm Velero pods/components are running.
정답：
설명：
See the solution below in Explanation:
Explanation:
* Install OADP via Web Console
* Operators # OperatorHub # search OADP / OpenShift API for Data Protection # Install
* Explanation: This operator manages Velero and backup integrations.
* Verify the operator CSV is installed
* oc get csv -A | grep -i -E "oadp|data protection|velero"
* Confirms installation succeeded.
* Verify pods in the OADP namespace (commonly openshift-adp)
* oc get pods -n openshift-adp
* You should see Velero/OADP-related pods in Running state.
질문 # 18
Create a full application backup (resources + PV data)
Task Information : Create a Velero backup of namespace orders including PV snapshots.
정답：
설명：
See the solution below in Explanation:
Explanation:
* Confirm resources and PVCs exist
* oc -n orders get all
* oc -n orders get pvc
* Ensures there is something meaningful to back up.
* Create backup including volume snapshots
* velero backup create orders-full --include-namespaces orders --snapshot-volumes
* Captures Kubernetes objects and requests PV snapshots where supported.
* Check status/details
* velero backup describe orders-full --details
* velero backup logs orders-full
* Review warnings/errors and confirm snapshot actions.
질문 # 19
Add a second Identity Provider (HTPasswd) alongside LDAP
Task Information : Configure multiple identity providers by adding an HTPasswd IDP without removing the existing LDAP IDP.
정답：
설명：
See the solution below in Explanation:
Explanation:
* Create a local htpasswd file with a test user
* htpasswd -c -B -b /tmp/htpass.txt testuser RedHat123!
* -c creates a new file (use only once).
* -B uses bcrypt hashing (recommended).
* -b supplies password non-interactively (good for labs).
* Create the HTPasswd secret in openshift-config
* oc -n openshift-config create secret generic htpass-secret --from-file=htpasswd=/tmp/htpass.txt
* OAuth reads the htpasswd key from this secret.
* Edit OAuth and add the HTPasswd provider (keep LDAP intact)
* oc edit oauth cluster
Add another entry under spec.identityProviders:
- name: local-htpasswd
mappingMethod: claim
type: HTPasswd
htpasswd:
fileData:
name: htpass-secret
* This adds a second login option while preserving LDAP.
* Restart OAuth pods
* oc -n openshift-authentication delete pod -l app=oauth-openshift
* Ensures the updated list of identity providers is loaded.
* Verify login works for htpasswd user
* Log in via console using testuser.
* Confirm the user is created:
* oc get user testuser
질문 # 20
Service Accounts and RBAC - Grant Cluster Reader Role
정답：
설명：
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.
질문 # 21
......
EX380시험준비: https://www.itdumpskr.com/EX380-exam.html