弊社はお客様の皆様の利益を保証するために、あなたに高いクオリティのサービスを提供できて努力しています。今まで、弊社のXhs1991のEX380問題集はそのスローガンに沿って協力します。弊社の信頼できるEX380問題集を使用したお客様はほとんど試験に合格しました。
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration |
| Exam Number: | EX380 |
| Passing Score: | 210 (on a scale of 100-300) |
| Related Certifications: | Red Hat Certified Engineer (RHCE) Red Hat Certified Architect (RHCA) |
| Exam Duration: | 180 minutes |
| Certificate Validity Period: | 3 years |
| Real Exam Qty: | 15 |
| Exam Format: | Performance-based, Hands-on labs |
| Exam Price: | $400 USD |
| Available Languages: | English, Chinese (Simplified), Japanese |
| Sample Questions: | RedHat EX380 Sample Questions |
| Exam Way: | On-site at Red Hat certified testing centers or online proctored exam |
| Pre Condition: | Red Hat recommends taking the DO180 (Red Hat OpenShift Administration I) course or having equivalent knowledge before attempting this exam. Familiarity with Linux administration is strongly recommended. |
| Official Syllabus URL: | https://www.redhat.com/en/services/training/ex380-red-hat-certified-specialist-openshift-automation-and-integration-exam |
EX380認定試験は試験に関連する書物を学ぶだけで合格できるものではないです。がむしゃらに試験に要求された関連知識を積み込むより、価値がある問題を勉強したほうがいいです。効率のあがる試験問題集は受験生の皆さんにとって欠くことができないツールです。ですから、はやくXhs1991のEX380問題集を入手しましょう。これは高い的中率を持っている問題集で、ほかのどのような勉強法よりもずっと効果があるのです。これはあなたが一回で楽に成功できるを保証するめぼしい参考書です。
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 10
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.
質問 # 11
Silence an alert in Alertmanager
Task Information : Create an Alertmanager silence for a noisy alert for 2 hours, then confirm it's silenced.
正解：
解説：
See the solution below in Explanation:
Explanation:
* Find the alert name and labels
* Web console: Observe # Alerts # click the alert to view label set.
* Open Alertmanager silences
* Observe # Alerting # Alertmanager # Silences # Create silence
* Explanation: Silences mute alerts matching label filters.
* Create the silence
* Add matcher: alertname = < ALERT_NAME >
* Duration: 2 hours
* Save.
* Verify the alert shows as silenced
* The alert should indicate it is silenced in the UI.
質問 # 12
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.
質問 # 13
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.
質問 # 14
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.
質問 # 15
......
EX380関連受験参考書: https://www.xhs1991.com/EX380.html