RedHat的EX380考試認證是業界廣泛認可的IT認證，世界各地的人都喜歡RedHat的EX380考試認證，這項認證可以強化自己的職業生涯，使自己更靠近成功。談到RedHat的EX380考試,Testpdf RedHat的EX380的考試培訓資料一直領先於其他的網站，因為Testpdf有一支強大的IT精英團隊，他們時刻跟蹤著最新的 RedHat的EX380的考試培訓資料，用他們專業的頭腦來專注於 RedHat的EX380的考試培訓資料。
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration (EX380) |
| Exam Number: | EX380 |
| Certificate Validity Period: | 3 years |
| Exam Format: | Hands-on practical tasks in OpenShift and automation environments, Performance-based lab exam |
| Exam Price: | USD 400 (varies by region) |
| Related Certifications: | Red Hat Certified Specialist in OpenShift Administration Red Hat Certified Engineer (RHCE) Red Hat Certified System Administrator (RHCSA) |
| 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) |
| Available Languages: | English |
| Recommended Training: | Red Hat OpenShift Administration courses Red Hat Ansible Automation Platform training |
| 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 |
你是否正在為通過RedHat EX380認證考試而奮鬥？想早點實現通過RedHat EX380認證考試的目標嗎？你可以選擇我們的Testpdf為你提供的培訓資料。如果你選擇了Testpdf，通過RedHat EX380認證考試不再是一個夢想。
| 主題 | 簡介 |
|---|---|
| 主題 1 |
|
| 主題 2 |
|
| 主題 3 |
|
| 主題 4 |
|
| 主題 5 |
|
問題 #26
Kubeconfig Management - Set Credentials in Kubeconfig
答案：
解題說明：
See the solution below in Explanation:
Explanation:
Step 1: Ensure the client certificate and private key files are available.
The lab uses audit.crt and tls.key.
Step 2: Run the command:
oc config set-credentials audit --client-certificate audit.crt --client-key tls.key --embed-certs --kubeconfig audit.config Step 3: Confirm the user entry is written.
The lab output shows:
User "audit" set.
Detailed explanation:
This command creates or updates the audit user entry inside the kubeconfig file audit.config. It points the user to a client certificate and private key, and the --embed-certs option stores certificate material directly inside the kubeconfig rather than only referencing external files. That makes the kubeconfig more portable because it can be moved and used without separately copying the certificate files, provided the embedded content is valid. In certificate-based authentication, the private key proves client possession while the certificate presents the approved identity. If the certificate and key do not match, authentication will fail. This step does not yet define what cluster or namespace the user works against; it only defines the credential identity.
問題 #27
Backup and Restore - Fix SCC for Restored Application
答案：
解題說明：
See the solution below in Explanation:
Explanation:
Step 1: Identify the application namespace after restore.
The lab shows the namespace as my-app-namespace.
Step 2: Run the SCC assignment command:
oc adm policy add-scc-to-user anyuid -z default -n my-app-namespace
Step 3: Confirm the role binding is applied.
The lab output shows:
clusterrole.rbac.authorization.k8s.io/system:openshift:scc:anyuid added: "default" Detailed explanation:
After a restore, the application may fail if its pods require a security context not permitted by the default SCC allocation. This command grants the anyuid SCC to the default service account in the my-app-namespace project. The -z default syntax targets the default service account, which many restored workloads use if no custom service account is defined. The anyuid SCC allows containers to run with arbitrary user IDs, which some legacy or prebuilt images require. In OpenShift, SCC mismatches commonly cause pods to remain in pending or crash-related states. Assigning the proper SCC resolves those admission issues so workloads can start successfully. This step is therefore a post-restore operational fix to align security policy with application requirements.
問題 #28
Export and import container images (mirror to internal registry)
Task Information : Pull an image from an external registry, push it into the OpenShift internal registry, and update a deployment to use the mirrored image.
答案：
解題說明：
See the solution below in Explanation:
Explanation:
* Log in to OpenShift internal registry
* oc registry login
* Allows podman to push to the internal registry.
* Pull external image
* podman pull docker.io/library/nginx:1.25
* Gets the image locally.
* Tag for internal registry destination
* podman tag nginx:1.25 image-registry.openshift-image-registry.svc:5000/orders/nginx:1.25
* Uses the cluster service DNS name (works inside cluster network).
* Push to internal registry
* podman push image-registry.openshift-image-registry.svc:5000/orders/nginx:1.25
* Update deployment to use internal image
* oc -n orders set image deploy/web web=image-registry.openshift-image-registry.svc:5000/orders/nginx:
1.25
* Verify rollout
* oc -n orders rollout status deploy/web
* oc -n orders get pods -o wide
問題 #29
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.
問題 #30
Maintain group synchronization on a schedule (CronJob)
Task Information : Create a CronJob that runs LDAP group sync on a schedule using a service account that has the required permissions.
答案：
解題說明：
See the solution below in Explanation:
Explanation:
* Create a namespace for the sync job
* oc new-project id-sync
* Keeps the automation components organized.
* Create a service account for the sync job
* oc -n id-sync create sa group-sync
* CronJob runs under this SA identity.
* Grant cluster permissions to manage groups
* oc adm policy add-cluster-role-to-user cluster-admin system:serviceaccount:id-sync:group-sync
* In real environments you should scope down, but lab Task SIMULATIONs often accept cluster- admin for speed.
* Create a ConfigMap for groupsync.yaml and Secret(s) for bind password/CA
* Mount them into the job container.
* Create CronJob to run group sync
* Command inside job:
* oc adm groups sync --sync-config=/config/groupsync.yaml --confirm
* The CronJob ensures periodic reconciliation with LDAP.
* Verify job runs
* oc -n id-sync get cronjob
* oc -n id-sync get jobs
* oc -n id-sync logs job/ < job-name >
問題 #31
......
EX380考試內容: https://www.testpdf.net/EX380.html