EX280 Exam Dumps - RedHat Red Hat Certified Architect (RHCA) Questions and Answers

Solution:

$ oc adm policy add-cluster-role-to-user cluster-admin jobs

$ oc adm policy remove-cluster-role-from-group self-provisioner

system:authenticated:oauth

$ oc adm policy add-cluster-role-to-user self-provisioner wozniak

$ oc delete secret kubeadmin -n kube-system

Solution:

Switch to the project hosting the cronjob, if needed:

oc project cron-test

Create the service account:

oc create sa jupiter

Grant anyuid:

oc adm policy add-scc-to-user anyuid -z jupiter -n cron-test

Grant cluster-admin:

oc adm policy add-cluster-role-to-user cluster-admin system:serviceaccount:cron-test:jupiter

Update the cronjob:

oc patch cronjob cron-test -p '{"spec":{"jobTemplate":{"spec":{"template":{"spec":{"serviceAccountName":"jupiter"}}}}}}'

Verify:

oc get cronjob cron-test -o yaml | grep serviceAccountName

Notes:

The uploaded lab uses oc set sa cronjob.batch/cron-test jupiter, which is not the usual command form for CronJobs. Patching the pod template is the reliable method.

This task checks service account and privilege adjustments for scheduled workloads.

Solution:

Open the Web Console.

Switch to project start .

Navigate to: Workloads → Deployments

Select the target deployment.

Click the action menu and choose: Add Health Checks

Select Liveness Probe .

Configure the appropriate probe type:

HTTP

TCP

or Command

Enter the required endpoint or command based on the application.

Save the configuration.

Verify the deployment updates successfully and the pod status remains healthy.

CLI alternative if needed:

oc set probe deployment/ < deployment-name > --liveness --get-url=http://:8080/ --initial-delay-seconds=10

This task measures health-check configuration for workload self-recovery.

Solution:

Ensure you are in the correct project:

oc project qed

Set the service account on the deployment:

oc set serviceaccount deployment/gitlab-skdjfklj project1-sa

Verify:

oc get deployment gitlab-skdjfklj -o yaml | grep serviceAccount

oc describe deployment gitlab-skdjfklj

If required, restart rollout:

oc rollout restart deployment/gitlab-skdjfklj

This task checks workload identity assignment through service accounts.

Solution:

Create landing-pv.yaml:

apiVersion: v1

kind: PersistentVolume

metadata:

name: landing-pv

spec:

capacity:

storage: 1Gi

accessModes:

- ReadOnlyMany

nfs:

path: /open001

server: 192.168.2.2

persistentVolumeReclaimPolicy: Retain

Apply it:

oc apply -f landing-pv.yaml

Create landing-pvc.yaml:

apiVersion: v1

kind: PersistentVolumeClaim

metadata:

name: landing-pvc

spec:

accessModes:

- ReadOnlyMany

resources:

requests:

storage: 1Gi

storageClassName: nfs2

Apply it:

oc apply -f landing-pvc.yaml

Verify:

oc get pv

oc get pvc

oc describe pv landing-pv

oc describe pvc landing-pvc

This task validates persistent storage provisioning and claim binding concepts.

Solution:

Create the initial HTPasswd file with the first user:

htpasswd -c -B -b /tmp/htpass.txt bob indionce

Add the remaining users:

htpasswd -b /tmp/htpass.txt qwerty catalog

htpasswd -b /tmp/htpass.txt john john123

htpasswd -b /tmp/htpass.txt armstrong natasha123

htpasswd -b /tmp/htpass.txt natasha arthstrong

htpasswd -b /tmp/htpass.txt harry harry123

htpasswd -b /tmp/htpass.txt susan susuan123

Create the secret in openshift-config :

oc create secret generic ex280-secure --from-file=htpasswd=/tmp/htpass.txt -n openshift-config

Edit OAuth and add the HTPasswd identity provider:

oc edit oauth cluster

Use a valid structure like this:

spec:

identityProviders:

- name: ex280-idp-secure

mappingMethod: claim

type: HTPasswd

htpasswd:

fileData:

name: ex280-secure

Save and exit.

Restart OAuth pods:

oc delete pod -n openshift-authentication -l app=oauth-openshift

Verify:

oc get pods -n openshift-authentication

oc get oauth cluster -o yaml

This task validates OpenShift local authentication configuration through HTPasswd and cluster OAuth integration.

Solution:

$ oc project gru

$ oc get pods

$ oc get all | grep deployment

$ oc scale --replicas=5 deployment.apps/minion

$ oc get pods

Solution:

Switch to the correct project if needed:

oc project monday

Inject environment variables from the secret:

oc set env deployment/monday --from=secret/magic

Verify:

oc set env deployment/monday --list

oc describe deployment monday

Notes:

The uploaded lab references secret/file-secret, but Task 8 clearly intends the secret to be named magic .

In a real exam, match the actual secret name present in the cluster.

This task tests secret consumption by workloads through environment variable injection.

Solution:

Add the repository:

helm repo add do280-repo http://helm.ocp4.example.com/charts

Refresh repositories:

helm repo update

Install the chart:

helm install example-app do280-repo/etherpad

Verify:

helm list

oc get all

Notes:

The uploaded lab text appears to spell the chart name incorrectly as ehterpad.

In practice, use the actual chart name published in the repo. If the lab repo truly contains the typo, follow the repo index result.

This task tests Helm repository management and application deployment.