EX280 RedHat Red Hat Certified Specialist in OpenShift Administration exam Free Practice Exam Questions (2026 Updated)

Solution:

Switch to the target project:

oc project darpa

Create a YAML file, for example limitrange.yaml:

apiVersion: v1

kind: LimitRange

metadata:

name: darpa-limits

namespace: darpa

spec:

limits:

- type: Pod

max:

cpu: 300m

memory: 300Mi

min:

cpu: 5m

memory: 5Mi

- type: Container

max:

cpu: 300m

memory: 300Mi

min:

cpu: 5m

memory: 5Mi

default:

cpu: 100m

memory: 100Mi

Apply it:

oc apply -f limitrange.yaml

Verify:

oc get limitrange -n darpa

oc describe limitrange darpa-limits -n darpa

This task validates namespace-level defaulting and constraint policies for pod scheduling and resource consumption.

Solution:

Scale the deployment:

oc scale deployment httpd --replicas=5

Verify:

oc get deployment httpd

oc get pods -l app=httpd

Confirm the desired, current, and available replica counts match.

This task checks direct workload scaling using the OpenShift CLI.

Solution:

Run must-gather:

oc adm must-gather

Confirm the directory created, usually something like:

ls

Archive the directory:

tar -cvzf system10-4ktjl-l4kj5l-lk45j.tar.gz must-gather.local.*

Verify:

ls -lh *.tar.gz

Notes:

The lab text shows a tar command without source paths. A valid tar command must include the source directory or files.

Use the actual must-gather output directory generated in your environment.

This task validates support-data collection and cluster diagnostics handling.

Solution:

$ vim limit.yaml

# Edit the yaml file like below mentioned

apiVersion: "v1" kind: "LimitRange" metadata:

name: "resource-limits" spec:

limits:

- type: "Pod"

max:

cpu: "500m" memory: "300Mi"

min:

cpu: "10m" memory: "5Mi"

- type: "Container" max:

cpu: "500m" memory: "300Mi"

min:

cpu: "10m" memory: "5Mi"

defaultRequest: cpu: "100m" memory: "100Mi"

$ oc create -f limit.yaml --save-config -n bluebook

$ oc describe limitranges -n bluebook

Solution:

Generate the default template:

oc adm create-bootstrap-project-template -o yaml > template.yaml

Review and edit template.yaml if required.

Create the template in openshift-config:

oc create -f template.yaml -n openshift-config

Edit the cluster project configuration:

oc edit project.config.openshift.io/cluster

Add or update:

spec:

projectRequestTemplate:

name: project-request

Save and exit.

Create a test project:

oc new-project test123

Verify the template behavior:

oc get project test123 -o yaml

Notes:

The uploaded lab text shows projects.config.openshift.io cluster-admin; the standard resource is project.config.openshift.io/cluster.

This task checks cluster-wide customization of new-project creation behavior.

Solution:

$ oc project apples

$ oc create sa ex280sa

$ oc adm policy add-scc-to-user anyuid -z ex280sa

Solution:

$ sudo yum install httpd-tools -y

$ htpasswd -c -B -b htpasswd-file-upload armstrong indionce

$ htpasswd -B -b htpasswd-file collins veraster

$ htpasswd -B -b htpasswd-file aldrin roonkere

$ htpasswd -B -b htpasswd-file jobs sestiver

$ htpasswd -B -b htpasswd-file wozniak glegunge

$ oc create secret generic ex280-idp-secret --from-file

htpasswd=htpasswd-file -n openshift-config

$ oc get oauth/cluster -o yaml > oauth.yaml

$ vim oauth.yaml

$

esc-- > type :set paste -- > enter -- > insert -- > then paste the content for correct indent pasting

spec:

identityProviders:

- name: ex280-htpasswd mappingMethod: claim type: HTPasswd htpasswd:

fileData:

name: ex280-idp-secret

$ oc replace -f oauth.yaml

$ oc login -u armstrong -p indionce

$ oc login -u collins -p veraster

$ oc login -u aldrin roonkere

$ oc login -u jobs sestiver

$ oc login -u wozniak -p glegunge

#This below part of operation is completely optional and done just for handy login purpose

$ alias _kube="oc login -u kubeadmin -p ${kube_pass} ${api_url}"

$ alias _armstrong="oc login -u armstrong -p ${armstrong}

${api_url}"

$ alias _collins="oc login -u collins -p ${collins} ${api_url}"

$ alias _aldrin="oc login -u aldrin -p ${aldrin} ${api_url}"

$ alias _jobs="oc login -u jobs -p ${jobs} ${api_url}"

$ alias _wozniak="oc login -u wozniak -p ${wozniak} ${api_url}"

$ _armstrong;_armstrong;_collins;_aldrin;_jobs;_wozniak;

Solution:

$ oc get all | grep deploy

$ oc set env --from=secret/magic deployment.apps/qed