BTW, DOWNLOAD part of RealValidExam EX380 dumps from Cloud Storage: https://drive.google.com/open?id=1K7S9n3-_O5HCes-VztoZsJEqR5_zi9g5
Our online staff is professionally trained and they have great knowledge on the EX380 study guide. So they can clearly understand your requirements and ideas and then help you make the right choices. When you have purchased our EX380 exam practice, but you do not know how to install it, we can also provide remote guidance to help you complete the installation. All in all, we will always be there to help you until you pass the EX380 Exam and get a certificate.
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Configure authentication and authorization | 15% | - Manage users and groups - Integrate with external identity providers - Configure RBAC (Role-Based Access Control) - Create and manage service accounts |
| Topic 2: Deploy and manage applications | 20% | - Create and manage deployments - Implement multi-container pods - Use ConfigMaps and Secrets - Configure application scaling and replication |
| Topic 3: Manage OpenShift Container Platform through CLI and Web UI | 15% | - Install and configure OpenShift cluster using CLI tools - Navigate and operate through the web console - Use oc and kubectl commands for cluster management |
| Topic 4: Implement and manage networking | 15% | - Manage network policies - Troubleshoot network connectivity issues - Configure Ingress and Egress policies |
| Topic 5: Implement CI/CD pipelines | 10% | - Integrate with external CI/CD tools - Configure OpenShift pipelines ( Tekton ) - Automate application deployments |
| Topic 6: Monitor and troubleshoot cluster | 15% | - Monitor cluster health and metrics - Troubleshoot common issues - Analyze logs and events |
| Topic 7: Manage storage for applications | 10% | - Manage storage classes - Configure persistent storage - Create and use persistent volume claims |
>> EX380 Advanced Testing Engine <<
The staffs of our EX380 training materials are all professionally trained. If you have encountered some problems in using our products, you can always seek our help. Our staff will guide you professionally. If you are experiencing a technical problem on the system, the staff at EX380 Practice Guide will also perform one-on-one services for you. And we work 24/7 online so that you can contact with us at anytime no matter online or via email on the questions of the EX380 exam questions.
NEW QUESTION # 18
Add a second Identity Provider (HTPasswd) alongside LDAP
Task Information : Configure multiple identity providers by adding an HTPasswd IDP without removing the existing LDAP IDP.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Create a local htpasswd file with a test user
* htpasswd -c -B -b /tmp/htpass.txt testuser RedHat123!
* -c creates a new file (use only once).
* -B uses bcrypt hashing (recommended).
* -b supplies password non-interactively (good for labs).
* Create the HTPasswd secret in openshift-config
* oc -n openshift-config create secret generic htpass-secret --from-file=htpasswd=/tmp/htpass.txt
* OAuth reads the htpasswd key from this secret.
* Edit OAuth and add the HTPasswd provider (keep LDAP intact)
* oc edit oauth cluster
Add another entry under spec.identityProviders:
- name: local-htpasswd
mappingMethod: claim
type: HTPasswd
htpasswd:
fileData:
name: htpass-secret
* This adds a second login option while preserving LDAP.
* Restart OAuth pods
* oc -n openshift-authentication delete pod -l app=oauth-openshift
* Ensures the updated list of identity providers is loaded.
* Verify login works for htpasswd user
* Log in via console using testuser.
* Confirm the user is created:
* oc get user testuser
NEW QUESTION # 19
Create and apply a MachineConfig (set MOTD on workers)
Task Information : Create a MachineConfig that writes /etc/motd on worker nodes.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Create the MachineConfig YAML (example content encoded in base64)
* apiVersion: machineconfiguration.openshift.io/v1
* kind: MachineConfig
* metadata:
* name: 99-worker-motd
* labels:
* machineconfiguration.openshift.io/role: worker
* spec:
* config:
* ignition:
* version: 3.2.0
* storage:
* files:
* - path: /etc/motd
* mode: 0644
* contents:
* source: data:text/plain;charset=utf-8;base64,VGhpcyBpcyBhIHdvcmtlciBub2RlLg==
* MachineConfig uses Ignition format; file content is typically base64.
* Apply it
* oc apply -f 99-worker-motd.yaml
* Watch worker MachineConfigPool roll out
* oc get mcp worker
* MCP will show Updating then Updated.
* Validate on a worker node (if you have node access)
* Confirm /etc/motd contains the expected text.
NEW QUESTION # 20
Service Accounts and RBAC - Grant Cluster Reader Role
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
Step 1: Confirm the service account exists in auth-audit.
It must exist before a role can be assigned to it.
Step 2: Run the command:
oc adm policy add-cluster-role-to-user cluster-reader system:serviceaccount:auth-audit:audit Step 3: Verify the binding is added.
The lab output shows:
clusterrole.rbac.authorization.k8s.io/cluster-reader added: "system:serviceaccount:auth-audit:audit" Detailed explanation:
This binds the cluster-reader cluster role to the audit service account. The full subject format system:
serviceaccount:namespace:name is required because OpenShift RBAC needs the exact service account identity. The cluster-reader role is broader than a project-scoped view role because it allows read-level access across cluster resources. This is appropriate for auditing or inspection use cases where the account must observe but not modify. The distinction between cluster roles and namespaced roles is important: cluster roles apply to non-namespaced resources and broad cluster visibility, while local roles are limited to individual projects. This Task is a classic RBAC operation that combines identity creation with controlled privilege assignment.
NEW QUESTION # 21
Maintain group synchronization on a schedule (CronJob)
Task Information : Create a CronJob that runs LDAP group sync on a schedule using a service account that has the required permissions.
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
* Create a namespace for the sync job
* oc new-project id-sync
* Keeps the automation components organized.
* Create a service account for the sync job
* oc -n id-sync create sa group-sync
* CronJob runs under this SA identity.
* Grant cluster permissions to manage groups
* oc adm policy add-cluster-role-to-user cluster-admin system:serviceaccount:id-sync:group-sync
* In real environments you should scope down, but lab Task SIMULATIONs often accept cluster- admin for speed.
* Create a ConfigMap for groupsync.yaml and Secret(s) for bind password/CA
* Mount them into the job container.
* Create CronJob to run group sync
* Command inside job:
* oc adm groups sync --sync-config=/config/groupsync.yaml --confirm
* The CronJob ensures periodic reconciliation with LDAP.
* Verify job runs
* oc -n id-sync get cronjob
* oc -n id-sync get jobs
* oc -n id-sync logs job/ < job-name >
NEW QUESTION # 22
GitOps and MachineConfig - Push MachineConfig to Git
Answer:
Explanation:
See the solution below in Explanation:
Explanation:
Step 1: Make sure the MachineConfig YAML has already been created or modified in the local Git repository.
This Task assumes the file change is ready to be committed.
Step 2: Run the command:
git commit -am "Add MachineConfig for motd" & & git push origin main
Step 3: Verify the commit succeeds and the push goes to the main branch.
The lab output shows:
[main 8d32a1] Add MachineConfig for motd
Detailed explanation:
This Task is part of a GitOps workflow. Instead of manually applying changes directly to the cluster, the desired configuration is stored in Git, and a GitOps controller such as Argo CD synchronizes the cluster to match the repository state. The command commits all tracked modified files with the message Add MachineConfig for motd and then pushes the change to the main branch. In this model, Git becomes the source of truth. A MachineConfig is typically used to manage node-level operating system configuration in OpenShift, so pushing it through GitOps ensures the change is auditable, repeatable, and reconciled declaratively. If the commit does not include the intended YAML, the synchronization mechanism will not apply the desired change.
NEW QUESTION # 23
......
You don't need to worry about wasting your precious time but failing to get the EX380 certification. Many people have used our EX380 study materials and the pass rate of the exam is 99%. This means as long as you learn with our EX380 Practice Guide, you will pass the exam without doubt. And we will give you one year's free update of the exam study materials you purchase and 24/7 online service. Now just make up your mind and get your EX380 exam dumps!
EX380 Reliable Exam Sims: https://www.realvalidexam.com/EX380-real-exam-dumps.html
BTW, DOWNLOAD part of RealValidExam EX380 dumps from Cloud Storage: https://drive.google.com/open?id=1K7S9n3-_O5HCes-VztoZsJEqR5_zi9g5