Solution for Ultimate Certified Kubernetes Administrator (CKA) Mock Exam Series

hello Guys ,
first of all i hope you’re doing well .

I’m preparing for CKA Exam and now I’m using the Ultimate Certified Kubernetes Administrator Exercice on kodekould platefome , and i’m wondering if i can get help with solution for all those exerices thanks in advance for sharing and your help .

thanks again

Hello @jobsaad

You can find here.

Thanks

Wai

Thanks for your reply , but i need solution for all the exercices in this course bellow (its another course on kodekloud plateform)

Ultimate Certified Kubernetes Administrator (CKA) Mock Exam Series

thanks again

Hi @jobsaad,
After submitting the exam, you can find the solution when the question got wrong in the lab itself.
At present, no solution is available on the GitHub page.

Regards,

1 Like

Hi @Singh-Rana
thanks a lot for your help .

I’m having issues while creating a persistent volume on question 10. When I created the pvc the accessmode config doesn’t configure the access mode ( leaves it blank). I have verified my yaml format. The PVC does create as well. See yaml below. Any advice on this? Thanks in advance

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: coconut-pvc-cka01-str
spec:
accessModes:
- ReadWriteMany
volumeMode: Filesystem
resources:
requests:
storage: 50Mi
storageClassName: coconut-stc-cka01-str
selector:
matchLabels:
#kubernetes.io/hostname: cluster1-node01
storage-tier: gold

Additionally, I even used this template to test and experienced the same behavior. From the kub docs

https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims

Two things will help us help you here:

  1. First, please link to the lab. It’s Q10, but for which Ultimate Mock Exam?
  2. It also helps, a lot, if you post your YAML using code blocks; these start with “```” and end with that. If you use the </> button in the edit block, it will create these triple-ticks for you in the right format, and you can past your YAML in between.

Hello - Thanks for replying. I was able to resolve my issue. Once I created a pod configured to consume the pv-claim. The PV and pvc were shown as bound with the accessmode ReadWriteMany. I assume this is due to the binding mode being configured with “WaitForFirstConsumer”