CKA (CNCF) exam-day guide
CKA · Prepare for the day ahead.
Your checklist
Original government-issued photo ID
Your name on the ID must match your exam registration exactly. Passport, driver's licence or national ID are typical; confirm the accepted ID types and the exact-match name rule in the provider's candidate handbook, and check that the ID is not expired.
Exam access link and portal credentials
Log in to your certification portal the day before and confirm the appointment appears. Verify the start time converted to your local time zone - portals often display UTC - and note the check-in window that opens before the start time.
Stable internet connection (with a backup option)
Prefer a wired connection over Wi-Fi. Run the provider's system/compatibility check in advance, and have a mobile hotspot available as a fallback that stays off and out of reach during the exam.
Working webcam and microphone
You will need these for ID verification and the room scan. Test both shortly before the exam and make sure no other application has claimed the camera.
Single-monitor setup
Disconnect or disable every additional display, including a laptop's extended desktop, before launching the exam. Multiple screens are generally prohibited; confirm the exact rule with the provider.
Cleared desk and room
Remove phones, smartwatches, headphones, earbuds, notes, printed material, books, extra keyboards and any other device from the desk and immediate area. Close the door and make sure nobody will enter the room.
Clear container of water (optional)
Some providers allow a plain, label-free container of water and nothing else. Do not assume this - confirm the allowed-items list for your exam before the day.
kubectl muscle memory, from memory only
No notes are allowed, so be able to type the patterns you rely on without reference: --dry-run=client -o yaml generators, kubectl config get-contexts / use-context, kubectl get ... -o wide, and your vim settings. Practise them until they are automatic.
Known navigation paths into the allowed documentation
Know by heart how to reach the pages you will actually use (kubectl cheat sheet, task pages for Services, PVCs, network policies, upgrades, etc.). Bookmarks may not persist into the locked-down exam browser, so rehearse from a blank tab.
Confirmed list of allowed reference sites
The allowed-resources list is published per exam and changes over time. Check it in your candidate handbook or exam instructions page before exam day and do not open anything outside that list.
A practised time plan
Know your average budget per task (roughly 6-8 minutes across the ~15-20 tasks in a 2-hour exam) and your habit of skipping, flagging and returning to hard tasks.
A quiet, uninterrupted environment and a charged laptop
Plug in power, silence notifications, quit chat and sync apps, and make sure you have a window of at least 2.5 hours with no interruptions.
Plan the day
Confirm the appointment time in your local time zone, run the provider's system test on the exact machine and network you will use, and verify your ID name matches your registration. Read the candidate handbook and the exam-specific instructions, and note the allowed-resources list and the published passing score (confirm the current number - for the CKA it has long been 66%).
Do one full timed mock under exam conditions: 2 hours, no notes, one screen, docs limited to the allowed site. Use it to find which task types eat your time, not to learn new topics.
Write down (mentally, since notes are banned) your standard playbook: read the task, check the target context, generate YAML imperatively, apply, verify with kubectl get/describe, then move on. Rehearse context switching - real exams use several clusters and contexts, and working in the wrong cluster scores zero.
Stop cramming new material. Do a light review of the imperative command patterns and the doc pages you will navigate to, then close the laptop.
Prep the room: clear the desk, test webcam and microphone, disconnect extra monitors, confirm the internet and the backup hotspot, charge devices, and sleep a full night. Fatigue costs more points than one more hour of study.
Eat, hydrate, use the bathroom, and put your phone away outside the exam room. Launch the exam session early - check-in typically opens about 30 minutes before the start and includes ID verification and a 360-degree room scan with the webcam; confirm the check-in window for your exam.
Once the proctor releases you, skim all tasks quickly and note which are quick wins and which are heavy. Do the quick wins first to bank points and calm nerves.
Work task by task with a budget of roughly 6-8 minutes each. Before every task, switch to the context named in the task and confirm it with kubectl config current-context. If a task overruns badly, flag it, leave a partial working state, and move on.
Return to flagged tasks and make sure each one has at least a partial answer - most tasks are weighted and partially correct work usually still earns credit. Sanity-check that objects you created are running/ready. Do not start a heavyweight task you cannot finish.
Results are typically emailed within about 24 hours, and the portal shows the score and a per-domain breakdown. Confirm the delivery time and retake terms with the provider before you leave the session.
Rules to check
Present an original, valid, government-issued photo ID at check-in; the name must match your registration. Photocopies and digital copies are generally rejected - confirm the exact accepted ID types with the provider.
Keep the desk and room clear of anything not explicitly permitted. Phones, smartwatches, headphones, notes and second screens are prohibited, and being seen with them can void your attempt.
Stay in view of the camera and inside the room for the whole session. The CKA is a 2-hour performance-based exam with no scheduled break - confirm the break and away-from-desk policy with the provider before the day.
Use only the reference material the provider lists for this exam. Opening other websites, chatting with anyone, or using AI/assistance tools is a conduct violation, even if the window is only briefly visible.
Aim for correct, working clusters rather than pretty YAML. Scoring is automated against the resulting cluster state, so resources that are created but not functional typically earn no credit - verify with kubectl get/describe.
Do not fight the environment. If the exam console, a cluster or the proctor connection misbehaves, raise it with the proctor or support immediately through the channel provided; problems reported after submission are much harder to resolve.
Submitting early does not improve your score, and there is usually no penalty for using the full time. Use remaining minutes to verify rather than to submit.
Retakes, score validity periods and any language-based time accommodation (a time extension may be available if the exam is not in your first language) are provider policies - confirm your specific entitlements with the provider rather than assuming.