Is there any way we can get at the CKA mock exam assertions?

Kubernetes
#1

I am taking my exam in a day and I’ve been using the CKA mock exams for ~3 months, so, i’ve gotten to know these questions pretty well i’d say. There are a handful however, that i get marked as incorrect and I cant for the life of me figure out how. Not to get too far off track: for example, in the db secrets one where you can’t edit the pod so you’ve got to adjust the keys and the secret name to fix, I can clearly see the requirements are met - all my pods running, zero errors in the logs, and zero restarts yet it is marked incorrect? The install etcd one where the solution is to pull the tarball when it can be installed via apt!? The k8s docs do not (as far as i can find) show you the steps you’re suggesting. Since you’re not allowed to leave the kubernetes.io domain, how would anyone be able to do this without the info? I digress, the point of this question is to ask if there’s any way to actually see the entire assertion, the command you’re running to validate the answers, or Anything for some introspection?

#2

I’d need to know the specific questions you’re talking about. Usually you can study the solutions (for both the regular mock exams as well as the Ultimate Mock Exams) and at least see what the grader was looking for.

#3

@kodekloud208
Please when referring to the questions, give us the SECTION name (at top of question) and the first few lines of the question. This helps us to find them quicker.

Lab number and question number are useless, because as you have likely noticed, the questions are randomized each time.

#4

I absolutely will do. I am doing another practice now so i will give more details. I can create a post specific to the questions i have issue with if that’s better. My main question really is about finding a way to see the actual test assertions for correctness? Maybe even some avail code to dig through?

#5

The lab marking scripts are not published. Those of us doing support don’t have access to the internal repos as we are not full time employees of KodeKloud.

When we think there is something wrong, we do have the ability to raise tickets in the backlog for lab engineers to investigate.

There are some known bugs for which there are already backlog tickets. You may have hit some of these.