Someone asked me to share my CKS exam tips: The best advice I got on the test wa . . .

Pete Wall:
Someone asked me to share my CKS exam tips:
The best advice I got on the test was about time management:
For each question,

  1. If you have no clue about how to answer it, mark it and skip. Otherwise, try to answer it and see if you can get it right in the first pass
  2. If something goes wrong, try to fix it once or twice (if fast). If that fails, mark it and move on.
  3. When you’ve gone through all the problems, go back and fix the ones you attempted, but skipped
  4. After that, try working on the ones you skipped outright.
    If, after that, you still have time, do what you can to double-check your answers. For example, if you’re supposed to restrict access to a pod from a certain namespace (e.g NetworkPolicy questions), try spinning up a pod from that namespace and see if the NetPol successfully prevents network access. This can be time consuming, so only do this if you can do it fast and if you feel like the extra test would help you feel confident in the answer.

Finally, by the time you’re taking a CKS exam, you should be comfortable with k8s things, especially kubectl. Now there are other external tools like AppArmor, Falco, Trivy, etc… It’s worth your time getting familiar with their CLIs. Run through the labs on KodeKloud a few times.

Good luck!

Pete Wall:
This is in no way saying what was or was not on my exam, FYI. Your questions will be different than mine.

Lakhwinder Singh:
@Pete Wall congratulations on clearing the exam and thank you for tips. This is super helpful.

Lakhwinder Singh:
btw, how many times did you go through labs before you appeared for the exam? and how difficult did you find the exam?

Pete Wall:
I went through the whole KodeKloud training. Then when I did the KodeKloud practice exams, I noted which things I felt weak on. Then I did those labs again.

Lakhwinder Singh:
cool, thank you @Pete Wall appreciate these tips

Prashant Bhosale:
@Pete Wall Thanks