学歴は実力と等しくなく、能力とも等しくないです。本当の能力は実践で鍛えたもので、学歴と直接な関係がないです。「私はだめです。」と思わないでください。RedHatのEX380試験に申し込んだあなたは自分が合格できないなんてを心配だったら、Jpshikenの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) |
| Certificate Validity Period: | 3 years |
| Real Exam Qty: | Performance-based exam (typically 1–3 hands-on tasks) |
| Available Languages: | English |
| 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 |
| Exam Format: | Hands-on practical tasks in OpenShift and automation environments, Performance-based lab exam |
| Recommended Training: | Red Hat Ansible Automation Platform training Red Hat OpenShift Administration courses |
| Exam Registration: | Red Hat Training and Exams Red Hat Certification Catalog |
| 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 |
EX380問題集を手に入れる前のサービスであれば、アフタサービスであれば、弊社はお客様の皆様の認めを得られるために、皆様の質問をすぐに返答できて準備しています。我々の社員は全日中で客様のお問い合わせをお待ちしております。あなたはJpshikenのEX380問題集について、何の質問があると、メールで我々のメールアドレスに送ったりすることができます。
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
質問 # 23
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.
質問 # 24
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.
質問 # 25
Create and use a service account token via kubeconfig
Task Information : Create SA ci-bot in ci namespace and generate a kubeconfig that authenticates using its token.
正解：
解説：
See the solution below in Explanation:
Explanation:
* Create namespace and service account
* oc new-project ci
* oc -n ci create sa ci-bot
* The SA will represent automation access.
* Grant permissions (example: edit in namespace)
* oc -n ci policy add-role-to-user edit system:serviceaccount:ci:ci-bot
* Without permissions, token auth succeeds but API actions are denied.
* Generate token (TokenRequest)
* TOKEN=$(oc -n ci create token ci-bot)
* OCP issues a short-lived token by default (good practice).
* Create kubeconfig using the token
* oc config set-cluster lab --server="$(oc whoami --show-server)" \
* --insecure-skip-tls-verify=true --kubeconfig=ci-bot.kubeconfig
* oc config set-credentials ci-bot --token="$TOKEN" --kubeconfig=ci-bot.kubeconfig
* oc config set-context ci --cluster=lab --user=ci-bot --namespace=ci \
* --kubeconfig=ci-bot.kubeconfig
* oc config use-context ci --kubeconfig=ci-bot.kubeconfig
* This produces a self-contained kubeconfig for CI automation.
* Test access
* oc --kubeconfig=ci-bot.kubeconfig get pods
質問 # 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
Identity Management - Create HTPasswd Secret
正解：
解説：
See the solution below in Explanation:
Explanation:
Step 1: Open a terminal with oc access to the cluster.
This Task is CLI-driven and targets the openshift-config namespace.
Step 2: Run the command:
oc create secret generic rhds-ldap-secret --from-literal bindPassword=redhatocp -n openshift-config Step 3: Verify that the secret is created successfully.
The lab output shows:
secret/rhds-ldap-secret created
Detailed explanation:
This step creates a generic secret named rhds-ldap-secret in the openshift-config namespace. The secret stores a key called bindPassword with the value redhatocp. In an identity-provider or LDAP integration workflow, the bind password is used by OpenShift when connecting to the external directory service. Storing this value in a secret is the correct operational pattern because authentication material should not be embedded directly into configuration objects. The openshift-config namespace is specifically important because cluster authentication configuration commonly references secrets and configmaps from that namespace. If the secret name or key is wrong, the authentication configuration that depends on it may fail to validate or connect properly.
質問 # 28
......
EX380学習指導: https://www.jpshiken.com/EX380_shiken.html