Marco Uhland

IT Consultant

Exam Experience and the problems encountered

In this article, which is a supplement to the article from Christoph Stifel, I write about my experience with the CKA Exam.

 

At the time I completed the CKA-Certificate the weights were divided as follows:

  • Troubleshooting 30%
  • Cluster Architecture, Installation & Configuration 25%
  • Services & Networking 20%
  • Workloads & Scheduling 15%
  • Storage 10%

I will not talk in depth about the preparation or the exam environment as Christoph already covered this in his article. Just one thing about preparation: Before starting your exam, you should be executing the environment testing script available on their scheduling page. This tests whether all requirements are met.

Troubleshooting

While I was taking my CKA I encountered some problems. First there was an error message saying “Connection to the Proctor Lost” and I couldn’t continue with my tasks first. After a few minutes of waiting, it seemed that the proctor was reconnected and I could continue, but it costed me about 10 minutes of my time. I still managed to finish just in time, but it would have been good to have a few minutes to check the exercises again.

It is also possible that the proctor cannot connect again. Your exam will be cancelled then and you will have to schedule a new one. You should also consider the support in this case, so it won’t count as a failed attempt.

To avoid this problem you should check your internet connection before starting the exam. You should also consider using a LAN cable instead of a wireless connection, as it is more reliable. Also disable any automatic downloads while the time of the exam to avoid any connection problems.

The second problem I encountered while taking the exam was about the terminal window. There was a problem when entering long commands. The command-line did not start a new line but instead overwrote the beginning of the command. The commands still worked as excepted, but it was hard to check the syntax of the command because you couldn’t see the full entry. My proctor also didn’t know how to fix this problem, so I just had to work like this. A little workaround is, typing your command in the notepad of the exam-environment and copy-paste it to the terminal.

Also make sure you got a camera on your laptop with a sufficient resolution. You have to confirm your identity with an ID-Card or a passport. The proctor should be able to read the information on the ID-Card. Maybe you will encounter problems with the focus of the camera. To avoid this, you could test the focus of your camera before the exam starts.

Some useful tips
  1. Stay calm, if you are prepared for the exam you won’t run out of time.
  2. Think straight-forward and fulfill the questions as they are asked. Not more, not less
  3. Know the Kubernetes documentation as you are allowed to use it in the exam.
  4. Mark questions you are not sure about and come back to these later.

Kubernative GmbH
Ziegelei 9
72336 Balingen

Telefon:
Mail:
Internet:

+49 7433 2781296
Diese E-Mail-Adresse ist vor Spambots geschützt! Zur Anzeige muss JavaScript eingeschaltet sein!
www.kubernative.net

Ein Tochterunternehmen der
ARWINET GmbH besuchen

Wir nutzen Cookies auf unserer Website. Einige von ihnen sind essenziell für den Betrieb der Seite, während andere uns helfen, diese Website und die Nutzererfahrung zu verbessern (Tracking Cookies). Sie können selbst entscheiden, ob Sie die Cookies zulassen möchten. Bitte beachten Sie, dass bei einer Ablehnung womöglich nicht mehr alle Funktionalitäten der Seite zur Verfügung stehen.