Exam Code: EX380
Exam Name: Red Hat Certified Specialist in OpenShift Automation and
Integration exam
Associate Certification: Red Hat Certified Specialist in OpenShift
Automation and Integration
Samples: 7Q&As
Save 40% on Full EX380 Exam Dumps with Coupon “40PASS”
EX380 exam dumps provide the most effective material to study and
review all key Red Hat Certified Specialist in OpenShift Automation and
Integration exam topics. By thoroughly practicing with EX380 exam dumps,
you can build confidence and pass the exam in a shorter time.
Practice EX380 exam online questions below.
1. SIMULATION
Task SIMULATION 2
Identity Management C Create HTPasswd Secret
Answer:
, 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.
2. SIMULATION
Task SIMULATION 8
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.
Answer:
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
Exam Name: Red Hat Certified Specialist in OpenShift Automation and
Integration exam
Associate Certification: Red Hat Certified Specialist in OpenShift
Automation and Integration
Samples: 7Q&As
Save 40% on Full EX380 Exam Dumps with Coupon “40PASS”
EX380 exam dumps provide the most effective material to study and
review all key Red Hat Certified Specialist in OpenShift Automation and
Integration exam topics. By thoroughly practicing with EX380 exam dumps,
you can build confidence and pass the exam in a shorter time.
Practice EX380 exam online questions below.
1. SIMULATION
Task SIMULATION 2
Identity Management C Create HTPasswd Secret
Answer:
, 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.
2. SIMULATION
Task SIMULATION 8
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.
Answer:
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
