The instructions for Question 8 is unclear

Create the below admission-configuration inside /root/CKS/ImagePolicy directory in the controlplane

use this YAML file:

apiVersion: apiserver.config.k8s.io/v1
kind: AdmissionConfiguration
plugins:

• name: ImagePolicyWebhook
  configuration:
  imagePolicy:
  kubeConfigFile: /etc/admission-controllers/admission-kubeconfig.yaml. ## Does not exist
  allowTTL: 50
  denyTTL: 50
  retryBackoff: 500
  defaultAllow: false

#The /root/CKS/ImagePolicy is mounted at the path /etc/admission-controllers directory in the kube-apiserver. So, you can directly place the files under /root/CKS/ImagePolicy.
#---snippet of the volume and volumeMounts (already added to apiserver config)
containers:
.
.
.
volumeMounts:

• mountPath: /etc/admission-controllers
  name: admission-controllers
  readOnly: true
  volumes:
• hostPath:
  path: /root/CKS/ImagePolicy/
  type: DirectoryOrCreate
  name: admission-controllers

update the kube-apiserver command flags and add ImagePolicyWebhook to the enable-admission-plugins flag

• --admission-control-config-file=/etc/admission-controllers/admission-configuration.yaml
• --enable-admission-plugins=NodeRestriction,ImagePolicyWebhook

The Seccomp in Kubernetes section mentions to use the below amicontained image to check the status of Seccomp and syscalls.

References:
https://github.com/kodekloudhub/certified-kubernetes-security-specialist-cks-course/blob/main/docs/04-System-Hardening/20-Implement-Seccomp-in-Kubernetes.md
https://kodekloud.com/topic/implement-seccomp-in-kubernetes/

The image r.j3ss.co/amicontained is no longer available in the dockerhub.
docker run r.j3ss.co/amicontained amicontained

Unable to find image 'r.j3ss.co/amicontained:latest' locally
docker: Error response from daemon: Get "https://r.j3ss.co/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.

Instead the below image can be used:
jess/amicontained
https://hub.docker.com/r/jess/amicontained

You may consider updating the session documentation / video for this.

The questions showing failed even if I just followed the solution presented.