Free RedHat EX380 Practice Exam with Questions & Answers

Run group sync with prune controls

oc adm groups sync --sync-config=groupsync.yaml --confirm --prune-whitelist=/tmp/whitelist.txt

Prune removes stale memberships/groups, but whitelist protects selected groups from pruning.

Verify group membership reflects LDAP

oc describe group < groupname >

Confirms removed users are no longer listed.

==========

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.

==========

Create target namespace

oc new-project gitops-demo

Destination must exist (unless Argo is configured to auto-create).

Create Application manifest

apiVersion: argoproj.io/v1alpha1

kind: Application

metadata:

name: demo-app

namespace: openshift-gitops

spec:

project: default

source:

repoURL: https://git.example.com/org/repo.git

targetRevision: main

path: manifests/demo

destination:

server: https://kubernetes.default.svc

namespace: gitops-demo

syncPolicy:

automated:

prune: true

selfHeal: true

automated: enables auto sync.

prune: removes deleted objects from Git.

selfHeal: corrects drift.

Apply Application

oc apply -f demo-app.yaml

Verify sync health

oc -n openshift-gitops get application demo-app -o yaml | grep -i -E "sync|health" -n

oc -n gitops-demo get all

==========

Step 1: Ensure the certificate file rhds_ca.crt is available in your current working directory or use the correct path.

The Task requires creating a configmap from this CA certificate file.

Step 2: Run the command:

oc create configmap rhds-ca-config-map --from-file ca.crt=rhds_ca.crt -n openshift-config

Step 3: Confirm the configmap is created.

The lab output shows:

configmap/rhds-ca-config-map created

Detailed explanation:

This creates a configmap named rhds-ca-config-map in the openshift-config namespace and maps the local file rhds_ca.crt to the key name ca.crt inside the configmap. This is important in external identity integration because OpenShift may need to trust a custom certificate authority when communicating with LDAP or another secured external service. By placing the certificate in a configmap, the authentication operator or related cluster configuration can reference it cleanly. The key name matters because many OpenShift resources expect a CA bundle key with a specific filename-like convention. If the file path is wrong, the command fails immediately. If the configmap name or key mapping is wrong, the authentication provider referencing it may not trust the external endpoint.

============

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.

============

Deploy event router resources

Apply a deployment/serviceaccount/rolebinding manifest for eventrouter:

oc apply -f eventrouter.yaml -n openshift-logging

Eventrouter watches event API and writes them to stdout (collected by logging).

Verify eventrouter pod is running

oc -n openshift-logging get pods | grep -i event

Trigger some events

oc -n default run evtest --image=busybox --restart=Never -- sleep 1

oc -n default delete pod evtest

Creation/deletion generates events.

Query logs for events

In the logging UI/backend, search for the namespace/pod name evtest or eventrouter messages.

Explanation: Validates that events are being converted to searchable logs.

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.

============

Step 1: Confirm that the repository being pushed to is the same repository watched by the GitOps/Argo CD application.

This linkage is essential because GitOps acts only on configured source repositories and paths.

Step 2: Commit the MachineConfig changes.

The lab uses:

git commit -am "Add MachineConfig for motd"

Step 3: Push the changes to the tracked branch.

The lab uses:

git push origin main

Step 4: Allow Argo CD to detect the repository change and begin synchronization.

In a standard GitOps model, the controller compares the Git repository to the cluster state and applies drift correction or new desired resources.

Detailed explanation:

This sub Task SIMULATION is the operational purpose behind the previous Git command Task SIMULATION . The point is not merely to store a file in Git; it is to update the declarative source that Argo CD uses to reconcile the cluster. Once the repository is updated, Argo CD detects the new commit and syncs the MachineConfig into the cluster according to its application definition. This demonstrates a core automation principle in OpenShift GitOps: administrators do not treat the cluster as the primary editable surface. Instead, they modify Git and let the automation layer enforce state. That provides traceability, peer review potential, rollback capability, and consistency across environments.

Log in to OpenShift internal registry

oc registry login

Allows podman to push to the internal registry.

Pull external image

podman pull docker.io/library/nginx:1.25

Gets the image locally.

Tag for internal registry destination

podman tag nginx:1.25 image-registry.openshift-image-registry.svc:5000/orders/nginx:1.25

Uses the cluster service DNS name (works inside cluster network).

Push to internal registry

podman push image-registry.openshift-image-registry.svc:5000/orders/nginx:1.25

Update deployment to use internal image

oc -n orders set image deploy/web web=image-registry.openshift-image-registry.svc:5000/orders/nginx:1.25

Verify rollout

oc -n orders rollout status deploy/web

oc -n orders get pods -o wide

==========

Create PDB

cat < < EOF | oc -n payments apply -f -

apiVersion: policy/v1

kind: PodDisruptionBudget

metadata:

name: api-pdb

spec:

minAvailable: 2

selector:

matchLabels:

app: api

EOF

minAvailable: 2 blocks evictions that would reduce availability below 2.

Verify PDB

oc -n payments get pdb

oc -n payments describe pdb api-pdb

==========