ppb
April 6, 2026, 8:59am
#1
Hi, I see that some of the checks are broken as even parts of the task were not considered.
First, the HTTP readiness probe that doesn’t check for anything
Another one is “is the busybox pod running?”
Another one is the ambiguity in blue-green deployment service. I used ClusterIP where it was not clearly specified we need to use NodePort. ClusterIP works just as well with curl
It would have helped if you had shared the complete screenshots with the lab and question numbers.
Are these from CKAD in-course mock exams or the Ultimate Mock Exam series?
ppb
April 6, 2026, 10:36am
#3
This is the first in CKAD ultimate mock exams, I think it were tasks 10, 19 and 20
I verified the labs and all worked fine at my end:
Q-19
I think you were not in the correct context while performing the task:
Q-20
Even that passed without much issue:
Q-5
The task clearly states that the application needs to be accessible from outside the cluster:
ppb
April 12, 2026, 7:37pm
#5
Hi, tried it the second time and tasks 19 and 20 are still broken, I am sure.
The task 19 I have already described here: Ckad-mock-1 (q19) - #4 by rob_kodekloud
For task 20, the pod is not detected as running. As you can see in -o yaml, the pod is deployed in correct cluster1.
$ k get pod ckad-pod-busybox -o yaml | grep -v '{"apiVersion":"v1"'
apiVersion: v1
kind: Pod
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
creationTimestamp: "2026-04-12T16:32:06Z"
generation: 1
name: ckad-pod-busybox
namespace: default
resourceVersion: "4817"
uid: 4faa1665-7749-4910-8c85-f0896477cf8b
spec:
containers:
- command:
- sleep
- "3600"
image: busybox
imagePullPolicy: Always
name: pods-simple-container
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
- mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: kube-api-access-ftft9
readOnly: true
dnsPolicy: ClusterFirst
enableServiceLinks: true
nodeName: cluster1-controlplane
preemptionPolicy: PreemptLowerPriority
...
$ k describe pod ckad-pod-busybox
Name: ckad-pod-busybox
Namespace: default
Priority: 0
Service Account: default
Node: cluster1-controlplane/10.244.198.212
Start Time: Sun, 12 Apr 2026 12:32:06 -0400
Labels: <none>
Annotations: <none>
Status: Running
IP: 10.42.0.10
IPs:
IP: 10.42.0.10
Containers:
pods-simple-container:
Container ID: containerd://7870cf9a745583e7b09b400eadbeb1800e77f9027c5814a19276d7ce43eae97d
Image: busybox
Image ID: docker.io/library/busybox@sha256:1487d0af5f52b4ba31c7e465126ee2123fe3f2305d638e7827681e7cf6c83d5e
Port: <none>
Host Port: <none>
Command:
sleep
3600
State: Running
Started: Sun, 12 Apr 2026 12:32:07 -0400
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ftft9 (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
kube-api-access-ftft9:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
Optional: false
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 16m default-scheduler Successfully assigned default/ckad-pod-busybox to cluster1-controlplane
Normal Pulling 16m kubelet Pulling image "busybox"
Normal Pulled 16m kubelet Successfully pulled image "busybox" in 420ms (420ms including waiting). Image size: 2222002 bytes.
Normal Created 16m kubelet Created container: pods-simple-container
Normal Started 16m kubelet Started container pods-simple-container