当社CertShikenは、EX380学習ダンプの革新性に高い注意を払っています。イノベーションへの投資を絶えず増やし、研究専門家チームのメンバーのためのインセンティブシステムを構築しています。専門家グループは、EX380試験実践ガイドの研究と革新を専門とし、最新の革新と研究結果をEX380クイズ準備にタイムリーに補足します。当社の専門家グループは、最新の学術的および科学的研究結果を収集し、EX380学習資料の更新における最新の業界の進歩を追跡します。
| Certification Vendor: | Red Hat |
|---|---|
| Exam Name: | Red Hat Certified Specialist in OpenShift Automation and Integration exam |
| Exam Number: | EX380 |
| Available Languages: | English |
| Passing Score: | Not disclosed |
| Exam Format: | Practical tasks, Performance-based, Hands-on lab |
| Exam Duration: | 240 minutes |
| Certificate Validity Period: | 3 years |
| Related Certifications: | Red Hat Certified Architect (RHCA) |
| Real Exam Qty: | Performance-based tasks, no fixed number |
| Exam Price: | $450 USD / €450 EUR |
| 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 |
CertShikenは当面最新のRedHatのEX380の認証試験の準備問題を提供している認証された候補者のリーダーです。弊社の資源はずっと改訂され、アップデートされていますから、緊密な相関関係があります。RedHatのEX380の認証試験を準備しているあなたは、自分がトレーニングを選んで、しかも次の問題を受かったほうがいいです。弊社の試験問題はほとんど毎月で一回アップデートしますから、あなたは市場で一番新鮮な、しかも依頼できる良い資源を得ることができることを保証いたします。
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
| トピック 6 |
|
質問 # 11
Configure RBAC roles with users and groups
Task Information : Grant edit to group dev-team in namespace payments, and grant view to user auditor1.
正解：
解説：
See the solution below in Explanation:
Explanation:
* Create (or switch to) the project
* oc new-project payments
* Namespace must exist before applying rolebindings.
* Grant edit to the group
* oc -n payments policy add-role-to-group edit dev-team
* Members of dev-team can modify most resources in payments.
* Grant view to a user
* oc -n payments policy add-role-to-user view auditor1
* auditor1 can read resources but not change them.
* Verify rolebindings
* oc -n payments get rolebinding
質問 # 12
Configure BackupStorageLocation and VolumeSnapshotLocation
Task Information : Configure OADP/Velero storage locations and confirm they show as Available.
正解：
解説：
See the solution below in Explanation:
Explanation:
* Create a secret for cloud credentials (S3-compatible example)
* oc -n openshift-adp create secret generic cloud-credentials \
* --from-file=cloud=/path/to/credentials
* Velero uses this secret to authenticate to object storage.
* Create/Update the DataProtectionApplication (DPA)
* Apply a DPA CR that defines:
* backupLocations (bucket, endpoint URL, region, etc.)
* snapshotLocations (if using snapshots)
* Verify BackupStorageLocation and SnapshotLocation
* velero backup-location get
* velero snapshot-location get
* Status should be Available, meaning storage config is valid.
==========
質問 # 13
Service Accounts and RBAC - Create Audit Service Account
正解：
解説：
See the solution below in Explanation:
Explanation:
Step 1: Ensure the target project exists.
The lab specifies the namespace/project auth-audit.
Step 2: Run the command:
oc create sa audit -n auth-audit
Step 3: Verify creation.
The lab output shows:
serviceaccount/audit created
Detailed explanation:
This creates a service account named audit in the auth-audit namespace. Service accounts provide non-human identities for workloads and automation processes running inside the cluster. They are also commonly used when controlled API access is needed for scripts, jobs, or external kubeconfig generation. Creating a dedicated service account instead of using the default one is good practice because it supports least privilege and clearer access tracking. In exam and administration scenarios, service accounts are often paired with explicit RBAC bindings to grant only the permissions needed for the intended Task SIMULATION . This step lays the identity foundation before assigning a role in the following Task SIMULATION .
質問 # 14
Configure and synchronize OpenShift groups from LDAP (group sync)
Task Information : Create an LDAP group-sync config, run a one-time sync, and confirm groups exist in OpenShift.
正解：
解説：
See the solution below in Explanation:
Explanation:
* Create a group sync config file (example groupsync.yaml)
* This file defines how OpenShift queries LDAP for groups and members.
* Run a one-time group sync
* oc adm groups sync --sync-config=groupsync.yaml --confirm
* --confirm actually applies changes (without it, it's a dry-run preview).
* Verify groups created/updated
* oc get groups
* oc describe group < groupname >
* Confirms group objects exist and membership is present.
質問 # 15
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.
質問 # 16
......
EX380絶対合格: https://www.certshiken.com/EX380-shiken.html