Course Introduction

​

What this mock exam series covers

• Comprehensive and challenging.
• Structured to reflect the real CKA exam weightages.
• Delivered across multiple Kubernetes clusters (four clusters total), with some clusters dedicated to specific knowledge areas.

• Switch kubectl contexts to access any of the four clusters.
• SSH into individual nodes for deeper troubleshooting where required.

​

CKA domain breakdown (exam weightage)

​

Getting started with a lab

​

Common kubectl context and cluster commands

kubectl config use-context cluster3

kubectl config get-clusters

• cluster1: two worker nodes (cluster1-node01, cluster1-node02)
• cluster3: single control-plane node (cluster3-controlplane, version 1.24 as of recording)

kubectl config current-context

​

Typical task: decode a Secret and save it on the student node

1. Ensure you are on the correct cluster/context:

kubectl config use-context cluster3

2. Confirm the namespace exists and list secrets in that namespace:

kubectl get ns
kubectl get secrets -n beta-ns-cka14-arch

3. View the Secret in YAML to see the base64-encoded data:

kubectl get secret beta-sec-cka14-arch -n beta-ns-cka14-arch -o yaml

4. Copy the base64 string shown under data, then decode and redirect to the required file on the student node:

echo 'VGhpcpyB0aGlgc2VjcmVtV0lQbw==' | base64 -d > /opt/beta-sec-cka14-arch

5. Verify the file contents:

cat /opt/beta-sec-cka14-arch

​

Useful secret inspection variants

• To decode a specific key from the Secret without saving:

kubectl get secret beta-sec-cka14-arch -n beta-ns-cka14-arch -o jsonpath='{.data.<key>}' | base64 -d

​

Navigating multiple questions and sections

• The exam is time-boxed. If you exceed the allotted time, the exam will end automatically and be validated.
• You may click the “End Exam” button at any time to trigger immediate validation and view your score.

​

Example walkthrough snippets

• Switch context and monitor logs:

kubectl --context cluster1 logs -f color-app-cka13-arch

• Create a ServiceAccount, ClusterRole, ClusterRoleBinding, and validate permissions (RBAC practice):

kubectl --context cluster1 create serviceaccount my-service-account
kubectl --context cluster1 create clusterrole my-cluster-role --verb=get,list,watch --resource=pods
kubectl --context cluster1 create clusterrolebinding my-cluster-role-binding --clusterrole=my-cluster-role --serviceaccount=default:my-service-account
kubectl --context cluster1 auth can-i get pods --as=system:serviceaccount:default:my-service-account
# Expected output:
# yes

• A simple keep-alive loop you might use while debugging locally:

while true; do echo hello; sleep 10; done

​

Best practices for taking these mock exams

• Always set the indicated kubectl context before starting a question.
• Read each task carefully: note the namespace, resource names, and exact file paths required (e.g., /opt/...).
• Use kubectl -n <namespace> get ... and -o yaml/-o jsonpath frequently to inspect current state.
• When decoding base64 strings, redirect output to the exact path specified by the task.
• Keep an eye on the clock and prioritize higher‑weighted tasks first.

​

Links and references

• Certified Kubernetes Administrator (CKA) preparation course — KodeKloud
• Kubernetes Documentation
• Basic kubectl reference: kubectl --help