CKA (Other exams) exam-day guide
CKA · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the same ID document you used when registering. The name must match your registration exactly. If your ID uses a different script or a shortened form of your name, confirm with the provider before exam day whether it will be accepted. needs_review: exact accepted ID types and any secondary-ID requirement are set by the Linux Foundation / PSI and can change - confirm with the provider.
Exam appointment confirmation and session details
Know your appointment time, time zone, and the provider's check-in window. Save the confirmation email and any session/launch link or access code offline (screenshot or local file) so a mail outage does not block you.
Test your computer and network ahead of time
Run the provider's system compatibility check on the exact machine and network you will use. Confirm webcam, microphone, browser version, and bandwidth. Repeat the check the morning of the exam.
Stable wired internet connection
Prefer a wired Ethernet connection over Wi-Fi, and have a fallback (mobile hotspot) ready. Confirm with the provider whether a disconnection pauses your clock or counts against your time. needs_review: reconnect and time-credit policy.
Quiet, private, well-lit room
Use a room with a closed door, no other people, no second screen, and no papers or notes on the desk. A proctor will likely ask for a 360-degree room scan with the webcam. Clear the desk before check-in.
Working webcam and microphone
You will be monitored and likely recorded. Test both devices in advance, and check that your face and hands are visible and the lighting does not silhouette you.
Close every other application
Shut down chat, mail, screen-sharing, VPN (unless required), and anything that could pop up or be flagged. Disable notifications and OS update prompts for the exam window.
Know the exam environment before you start
The CKA is a hands-on, performance-based exam taken in a live terminal environment with a remote desktop. Practise in a similar setup: a browser-based terminal, one screen, no copy-paste from outside the environment, and the exam's documentation access. needs_review: current environment details, allowed browser tabs, and documentation access rules - confirm with the provider.
Cluster-context and kubectl speed habits
You will work across multiple clusters. Before exam day, make kubectl config get-contexts and kubectl config use-context reflex, and set up a fast alias k=kubectl and shell completion in your practice environment so the motions are automatic.
Time-budget plan written down
Decide in advance how you will triage: read all questions, do easy high-value ones first, flag and skip long ones, and reserve the last 10–15 minutes for verification. Write the plan on paper now; you will not be allowed notes during the exam.
Backup plan for technical failure
Know the provider's support contact and how to raise an issue during the exam. If the session fails, note the time and details. Confirm with the provider how incidents are handled and whether they affect scoring. needs_review.
Water and bathroom break before check-in
Take care of these before the session starts. Confirm with the provider whether unscheduled breaks are allowed and how they affect your clock. needs_review: break policy.
Plan the day
Shift from learning to drilling. Do timed hands-on labs on the exam's core domains: cluster architecture and etcd backup/restore, workloads and scheduling, services and networking, storage, and troubleshooting. Practise kubectl under time pressure: create and edit objects with kubectl run, kubectl create, kubectl expose, and kubectl edit; use kubectl explain and kubectl api-resources to look things up fast. Rehearse the motions you will need on exam day: switching contexts, generating YAML with --dry-run=client -o yaml, and applying it.
Confirm logistics: re-read the provider's candidate handbook, verify your appointment time in your local time zone, run the system check, and test your ID against the registration name. Confirm with the provider any uncertainty about allowed materials, documentation access, and the retake policy.
Protect your sleep and stop cramming new topics 24–36 hours out. A rested candidate troubleshoots faster than a tired one. Do one light review pass over your own notes on common failure modes (wrong namespace, wrong context, missing -n, selector mismatches, and unready nodes).
Do a short, calm practice session only. Verify the room setup: desk clear, door closable, lighting good, webcam and mic working, wired network connected. Charge devices and note the support contact. Set two alarms. Go to bed at a normal hour.
Eat, hydrate, and use the bathroom. Re-run the system check, close all other apps, and silence your phone and put it out of reach. Join the check-in early - the ID check and room scan take time, and you do not want to start late. Have your ID in hand.
Read the instructions and note the total time and number of questions. Skim the whole question list and mentally tag each as quick, medium, or long. Start with the quick wins to bank points and build momentum.
Work in passes. For each task, confirm the cluster context and namespace before acting, then verify the result (kubectl get, describe, logs, or a curl from a pod) before moving on. If a task stalls, flag it and move on; return later with fresh eyes. Watch the clock at every quarter mark.
Stop starting new long tasks. Verify that the objects you created are in the right namespace and context and are actually running or ready. Re-check any flagged items you can finish quickly. Submit before time expires, and confirm the submission screen.
Rules to check
Follow the provider's rules on identity and environment exactly: present the registered ID, complete the room scan, and keep your face and hands visible. If anything about your setup is unusual, tell the proctor before starting rather than after being flagged.
Do not use unauthorized assistance, notes, second screens, phones, or other people. The CKA is a hands-on exam; the environment is monitored, and suspected violations can lead to invalidation. Confirm with the provider what materials and documentation are permitted inside the exam environment.
Treat the exam as a live production cluster. Only change what the question asks for; do not delete unrelated resources or run destructive commands outside the scope of a task. Grading is typically automated against the end state of the cluster, so verify that your changes actually took effect.
Mind the clock. The exam is time-limited and the clock generally does not stop for you. Confirm with the provider how disconnections, technical incidents, and unscheduled breaks are handled. needs_review.
Do not expect partial credit to be obvious. Automated scoring checks specific end states. If a task is ambiguous, do the most standard, verifiable version and move on. Confirm with the provider how partial credit and retakes work. needs_review: scoring and retake policy.
Keep the environment clean: close other applications, disable notifications, and do not attempt to copy exam content out. Sharing or reproducing exam questions violates the provider's terms.
If something goes wrong - a lost connection, a broken task, or a proctor request you do not understand - stop and use the provider's support or chat channel immediately, and note the time. Do not try to fix it silently and lose minutes.
Read each question fully before acting. The most common avoidable losses are wrong context, wrong namespace, and a resource that was created but never verified. Confirm the provider's current exam objectives and weighting on its site before your final review, since they change over time. needs_review.