KaoGuTi有很好的的售後服務。如果你選擇購買KaoGuTi的產品，KaoGuTi將為你提供每天24小時的線上客戶服務和提供一年的免費更新服務，及時的通知顧客最新的考試資訊讓客戶有充分準備。我們可以讓你花費少量的時間和金錢就可以通過IT認證考試。選擇KaoGuTi的產品幫助你的第一次參加的RedHat EX380 認證考試是很划算的。
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration exam |
| Exam Number: | EX380 |
| Available Languages: | English |
| Certificate Validity Period: | 3 years |
| Related Certifications: | Red Hat Certified Architect (RHCA) |
| Exam Format: | Performance-based, Practical tasks, Hands-on lab |
| Real Exam Qty: | Performance-based tasks, no fixed number |
| Exam Price: | $450 USD / €450 EUR |
| Exam Duration: | 240 minutes |
| Passing Score: | Not disclosed |
| 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 |
你已經報名參加了EX380認證考試嗎？是不是面對一大堆的復習資料和習題感到頭痛呢？KaoGuTi可以幫您解決這一問題，它絕對是你可以信賴的網站！只要你選擇使用KaoGuTi網站提供的資料，絕對可以輕鬆通過考試，與其花費時間在不知道是否有用的復習資料上，不如趕緊來體驗KaoGuTi帶給您的服務，還在等什麼趕緊行動吧。
| 主題 | 簡介 |
|---|---|
| 主題 1 |
|
| 主題 2 |
|
| 主題 3 |
|
| 主題 4 |
|
問題 #10
Identity Management - Create CA ConfigMap
答案：
解題說明：
See the solution below in Explanation:
Explanation:
Step 1: Ensure the certificate file rhds_ca.crt is available in your current working directory or use the correct path.
The Task requires creating a configmap from this CA certificate file.
Step 2: Run the command:
oc create configmap rhds-ca-config-map --from-file ca.crt=rhds_ca.crt -n openshift-config Step 3: Confirm the configmap is created.
The lab output shows:
configmap/rhds-ca-config-map created
Detailed explanation:
This creates a configmap named rhds-ca-config-map in the openshift-config namespace and maps the local file rhds_ca.crt to the key name ca.crt inside the configmap. This is important in external identity integration because OpenShift may need to trust a custom certificate authority when communicating with LDAP or another secured external service. By placing the certificate in a configmap, the authentication operator or related cluster configuration can reference it cleanly. The key name matters because many OpenShift resources expect a CA bundle key with a specific filename-like convention. If the file path is wrong, the command fails immediately. If the configmap name or key mapping is wrong, the authentication provider referencing it may not trust the external endpoint.
問題 #11
Integrate OpenShift with Keycloak (OIDC)
Task Information : Add a Keycloak (RH SSO) OpenID Connect identity provider to OpenShift OAuth and verify redirect/login works.
答案：
解題說明：
See the solution below in Explanation:
Explanation:
* Collect Keycloak details
* Issuer URL (realm), client ID, and client secret.
* Confirm Keycloak client has correct redirect URI for OpenShift OAuth callback.
* Create a secret with the OIDC client secret
* oc -n openshift-config create secret generic keycloak-oidc-secret \
* --from-literal=clientSecret=' < SECRET > '
* OAuth reads the OIDC client secret from this secret.
* Edit OAuth and add OpenID provider
* oc edit oauth cluster
Add under spec.identityProviders:
- name: keycloak
mappingMethod: claim
type: OpenID
openID:
issuer: "https://keycloak.example.com/realms/ocp"
clientID: "openshift"
clientSecret:
name: keycloak-oidc-secret
claims:
preferredUsername: ["preferred_username"]
name: ["name"]
email: ["email"]
* issuer must match Keycloak realm issuer URL.
* claims determines which token claims map to OpenShift username/name/email.
* Restart OAuth pods
* oc -n openshift-authentication delete pod -l app=oauth-openshift
* Verify by logging in through the web console
* You should be redirected to Keycloak, authenticate, then return to OpenShift.
* Confirm users/identities:
* oc get users
* oc get identities
問題 #12
Kubeconfig Management - Use Context
答案：
解題說明：
See the solution below in Explanation:
Explanation:
Step 1: Make sure the context already exists in the kubeconfig file.
This follows the context creation Task SIMULATION .
Step 2: Run the command:
oc config use-context audit --kubeconfig audit.config
Step 3: Confirm the active context switches successfully.
The lab output shows:
Switched to context "audit".
Detailed explanation:
This command activates the audit context inside the specified kubeconfig file. Once selected, subsequent oc commands using that kubeconfig will default to the cluster, user, and namespace associated with that context.
This is operationally important because many administration mistakes come from running commands against the wrong cluster or project. Using explicit context switching reduces that risk and makes the kubeconfig usable for the intended audit workflow. In exams and real environments alike, the context is what turns separate kubeconfig elements into a working session configuration. Without switching to the correct context, even a well-formed kubeconfig may not be used as expected.
問題 #13
Backup and Restore - Restore Application from Existing Backup
答案：
解題說明：
See the solution below in Explanation:
Explanation:
Step 1: Make sure Velero is installed and configured in the environment.
The Task SIMULATION assumes an existing backup named backup-app-daily is already present.
Step 2: Run the restore command:
velero restore create --from-backup backup-app-daily
Step 3: Confirm the restore request is submitted.
The lab output shows:
Restore request "backup-app-daily-2024" submitted successfully.
Detailed explanation:
This command instructs Velero to create a restore operation using the existing backup called backup-app- daily. Velero is commonly used to protect Kubernetes and OpenShift resources by backing up object definitions and, when configured, persistent data integrations. The command does not manually recreate resources one by one; instead, it leverages the metadata captured during backup. A successful restore submission means the request has been accepted, not necessarily that every object has already been fully restored. In practical administration, you would often follow this by checking restore status and validating the application namespace, pods, services, routes, and storage bindings. This lab Task SIMULATION focuses specifically on initiating the restore from the named backup source.
問題 #14
Integrate OpenShift with LDAP (create LDAP identity provider)
Task Information : Configure cluster OAuth to add an LDAP identity provider using an existing bind secret and CA ConfigMap , then verify login works.
答案：
解題說明：
See the solution below in Explanation:
Explanation:
* Verify prerequisites exist (Secret + ConfigMap)
* oc -n openshift-config get secret rhds-ldap-secret
* oc -n openshift-config get configmap rhds-ca-config-map
* OAuth LDAP configuration references these objects. If they don't exist, OAuth won't be able to bind to LDAP securely.
* Edit the cluster OAuth resource
* oc edit oauth cluster
* The oauth/cluster resource is where identity providers are defined.
* Add an LDAP identity provider entry (example structure) Add under spec.identityProviders:
* - name: corp-ldap
* mappingMethod: claim
* type: LDAP
* ldap:
* url: "ldaps://ldap.example.com:636/ou=People,dc=example,dc=com?uid"
* bindDN: "uid=openshift,ou=svc,dc=example,dc=com"
* bindPassword:
* name: rhds-ldap-secret
* ca:
* name: rhds-ca-config-map
* insecure: false
* attributes:
* id: ["dn"]
* name: ["cn"]
* preferredUsername: ["uid"]
* email: ["mail"]
* url: where to search for users and which attribute is used for login (here uid).
* bindDN + bindPassword: service account used for LDAP queries.
* ca: trusts the LDAP server CA for TLS.
* attributes: maps LDAP data into OpenShift user identity fields.
* Restart OAuth pods to load changes quickly
* oc -n openshift-authentication delete pod -l app=oauth-openshift
* This forces pods to restart and re-read the updated configuration.
* Verify the identity provider appears and users can log in
* In the web console login page, you should see the new provider (name may show as corp-ldap).
* After a successful login, confirm user objects appear:
* oc get users
* oc get identities
* OpenShift creates User and Identity objects upon first successful authentication.
問題 #15
......
EX380考試資料: https://www.kaoguti.com/EX380_exam-pdf.html