Also, stop memorising the vimrc setup and #kubectl command completion. These are now standard in the environment.
Be prepared for a horrible test environment. It's like a VNC web client connected to the Linux desktop with a terminal and Firefox. Copy and paste between the browser and local to the VM is janky.
It looks like can install extra software I was able to install gron, but I did this via apt. So anything that requires a curl shell install script may not work. I noticed that kubernetes.io search still listed community topics but did not let you click on them.
You're expected to know #JSONPath / #jq. If you're mind goes blank (remember you won't be able to search StackOverflow), get the format of the output from kubectl correct and then use grep (the old ways are the best).
If you do use #Kubernetes but in a managed environment (EKS, AKS, etc) you'll want to drill the labs on installing/maintaining clusters, etcd maintenance and deployments (including network policies, ingresses, etc). Same applies if you're used to an automated deployment CD environment like #ArgoCD. Remember "--dry-run=client --output yaml" is your friend.
Finally, be aware there are multiple cluster environments in the exam (questions will tell you which context to use), so if you know how to mod your PS1 prompt make sure it includes the output from "kubectl config current-context". Alternatively, create an alias
Do you have any useful tips? Share them in the replies?
Links
https://www.udemy.com/course/certified-kubernetes-administrator-with-practice-tests/
https://github.com/tomnomnom/gron