Online Access Free EX280 Practice Test

See the solution below in Explanation.
Explanation:
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.

See the solution below in Explanation.
Explanation:
Solution:
* Switch to the project:
oc project qed
* Create the service account:
oc create serviceaccount project1-sa -n qed
* Grant the SCC:
oc adm policy add-scc-to-user anyuid -z project1-sa -n qed
* Verify:
oc get sa project1-sa -n qed
oc adm policy who-can use scc anyuid
Why this matters:
* anyuid allows containers to run with arbitrary user IDs when an application requires it.
* This is a common administrative task in OpenShift for third-party container images.
This task validates service account creation and SCC assignment.

See the solution below in Explanation.
Explanation:
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.

See the solution below in Explanation.
Explanation:
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.

See the solution below in Explanation.
Explanation:
Solution:
* Create a file named mysql-db-conn.yaml:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: mysql-db-conn
spec:
podSelector:
matchLabels:
networking.k8s.io/v1/network: database
policyTypes:
- Ingress
ingress:
- from:
- namespaceSelector:
matchLabels:
team: devsecops
podSelector:
matchLabels:
deployment: my-web-mysql
ports:
- protocol: TCP
port: 3306
* Apply it:
oc apply -f mysql-db-conn.yaml
* Verify:
oc get networkpolicy
oc describe networkpolicy mysql-db-conn
This task tests namespace/pod label selection and application isolation using OpenShift networking policy controls.