EX280 Exam Dumps and Practice Questions

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:

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:

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:

$ oc project manhattan

$ oc create quota ex280-quota -- hard=memory=1Gi,cpu=2,pods=3,services=6,replicationcontrollers=3

$ oc get resourcequota

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.