CKA Exam Day Checklist: What to Do Before, During, and After

CKA exam day comes down to preparation you do before you sit down, discipline during the 2-hour exam, and patience while waiting for results. Most people who fail do not fail on knowledge. They fail on logistics, time management, or small preventable mistakes. This checklist covers everything you need to do before, during, and after the CKA exam so none of those things trip you up.

Print this page or bookmark it. Go through it the night before and the morning of your exam.

Before Exam Day: The Week Before

Start preparing your environment and mindset well before exam day. Scrambling to set up your desk 30 minutes before check-in is a recipe for stress and wasted mental energy.

Take Your Second Practice Session (2 to 3 Days Before)

Your CKA purchase includes two practice sessions. If you have not used both, use the second one 2 to 3 days before your exam. This is your dress rehearsal.

The practice sessions are deliberately harder than the real exam. If you score 55% to 60%, you are probably ready to pass the actual CKA. If you score below 40%, consider rescheduling. There is no shame in taking an extra week to prepare. The CKA study guide covers what to focus on if you need more time.

Do not take a practice session the night before. If you score poorly, it will shake your confidence. Two to three days out gives you time to review weak areas without cramming.

Verify Your ID

You need a valid government-issued photo ID. The name on your ID must exactly match the name on your exam registration. If there is a discrepancy, the proctor will not let you start.

Acceptable IDs:

• Passport
• Driver's license
• National ID card
• Military ID

The ID must not be expired. Check the expiration date now, not 10 minutes before the exam.

If your name on the ID does not match your registration (married name vs. maiden name, different transliteration of a non-Latin name), contact the Linux Foundation support before exam day to resolve it.

Prepare Your Physical Space

The proctoring requirements are strict. Your exam environment must meet these conditions:

• Clean desk. Nothing on your desk except your computer, keyboard, mouse, and your ID. No phones, notebooks, pens, sticky notes, books, or second monitors. Move everything off the desk.
• One monitor only. If you have a dual-monitor setup, disconnect or cover the second monitor. The proctor will ask you to show your desk via webcam, and a second screen is a violation.
• Working webcam and microphone. The proctor needs to see you and hear you throughout the exam. Test both before exam day.
• Stable internet. A dropped connection during the exam can cost you time and cause problems with the proctoring session. If your WiFi is unreliable, use a wired ethernet connection.
• Closed door. You need to be in a room alone with the door closed. No other people in the room. No pets walking across your keyboard.
• No headphones. You cannot wear headphones or earbuds during the exam.

Do a test run the day before. Sit at your exam desk, check that your webcam shows you and your desk clearly, verify your microphone works, and confirm your internet connection is stable. This takes 5 minutes and eliminates a whole category of exam-day problems.

Set Up Your Browser

The CKA runs through the PSI Secure Browser. You need to download and install this before exam day.

• Download the PSI Secure Browser from the link in your exam confirmation email
• Run the system check to verify your computer meets the requirements
• Close all other applications during the exam (the secure browser enforces this)

Do this the day before, not on exam morning. If there is a compatibility issue, you want time to fix it.

Exam Day Morning: The 60 Minutes Before

Two Hours Before the Exam

• Eat a real meal. Not a snack bar. You are about to concentrate for 2 hours straight. Low blood sugar makes you slow and error-prone.
• Drink water, but not too much. You can take bathroom breaks during the exam, but the clock does not stop.
• Avoid heavy caffeine if you are not used to it. Jitters and exam pressure are a bad combination. If you normally drink coffee, drink your normal amount.

30 Minutes Before the Exam

• Clear your desk completely. Only your computer, keyboard, mouse, and ID should be on the surface.
• Close every application on your computer except the PSI Secure Browser.
• Turn off notifications on your phone, then put the phone in another room. Not face-down on the desk. In another room.
• Close the door. Tell anyone in your house or apartment that you are taking an exam for the next 2.5 hours and cannot be interrupted.
• Have your ID next to your keyboard. The proctor will ask you to hold it up to the webcam.

15 Minutes Before the Exam

• Launch the PSI Secure Browser and log in.
• You can check in up to 15 minutes early. Do it. Early check-in gives you more time for the proctor verification process, which can take 5 to 10 minutes.
• The proctor will ask you to:
  • Show your ID to the webcam
  • Use your webcam to show a 360-degree view of your room
  • Show your desk surface (top, sides, under the desk)
  • Confirm you are alone in the room
  • Show that your desk is clean

Be patient during this process. Proctors follow a script. Comply quickly and politely.

The First 5 Minutes of the Exam

These first 5 minutes are not wasted time. They are an investment that pays off on every question for the rest of the exam.

Step 1: Set Up Your Terminal Environment

Before touching any questions, configure your terminal. This takes about 60 to 90 seconds and saves you minutes across the entire exam.

# Verify the kubectl alias (usually pre-set, but confirm)
alias k=kubectl

# Enable bash autocompletion for kubectl
source <(kubectl completion bash)
complete -F __start_kubectl k

# Set your preferred editor
export EDITOR=vim

Then configure vim for YAML editing:

cat <<EOF >> ~/.vimrc
set tabstop=2
set shiftwidth=2
set expandtab
set ai
EOF

These settings convert tabs to 2 spaces (matching Kubernetes YAML conventions) and enable auto-indent. Without them, a single tab character will break your YAML, and under exam pressure you might not notice why.

Step 2: Skim All Questions

Before answering anything, skim through every question. Look at the point values. Identify which questions look easy (2 to 3 minutes), medium (5 to 7 minutes), and hard (8+ minutes).

This takes about 2 to 3 minutes and gives you a mental map of the exam. You will know what is coming and can plan your time budget.

Some people prefer to answer questions in order. Others prefer to tackle easy questions first, then medium, then hard. Both approaches work. What does not work is starting with a hard question, getting stuck for 15 minutes, and then rushing through the rest of the exam.

Step 3: Check the Clock

Note the exact time remaining. You have 120 minutes for 15 to 20 questions. That is roughly 6 to 8 minutes per question on average, but some questions deserve more time than others.

Set mental checkpoints:

• At 90 minutes remaining, you should have completed about 25% of the total points
• At 60 minutes remaining, you should be past 50%
• At 30 minutes remaining, you should be past 75% and working on the hard questions you flagged

If you are behind these benchmarks, start skipping harder questions more aggressively.

During the Exam: Time Management

Time management is the single most important skill on exam day. More people fail the CKA from running out of time than from not knowing the material. Here is how to manage it.

The 7-Minute Rule

If you have been working on a question for 7 to 8 minutes without clear progress, flag it and move on. Come back later if time allows.

A 4% question is never worth 15 minutes. Three easier questions worth 5% each add up to 15%. Spending 15 minutes on the hard question means you traded 15% for 4%. That math loses exams.

The exam interface has a flag feature. Use it. Flag any question you skip so you can find it quickly during your review pass.

Context Switching Is Not Optional

Every question specifies which cluster to use. The first thing you do on every question, before reading the full task, is run the context switch command.

kubectl config use-context <cluster-name>
kubectl config current-context  # verify

If you solve a question on the wrong cluster, you get zero points. You will not know you made this mistake until you see your score. It is one of the most common CKA exam mistakes, and it is completely preventable. Our 10 CKA exam mistakes article covers this and other preventable errors.

Read the Full Question Before Starting

Under time pressure, your brain wants to start typing the moment it sees "create a Deployment." Resist this. Read the entire question first. Look for:

• The specified namespace (if you create the resource in the wrong namespace, zero points)
• Specific labels or annotations
• Resource requests and limits
• Exact image names and tags
• File paths where you need to save output
• Whether the question asks you to write the answer to a file or apply it to the cluster

Missing one of these details costs you the entire question. Reading the full question takes 15 to 20 seconds.

Use Imperative Commands

Generating YAML from imperative commands is 5x faster than writing YAML from scratch. Use this pattern for everything you can:

# Generate a Deployment
k create deployment web --image=nginx --replicas=3 --dry-run=client -o yaml > deploy.yaml

# Generate a Pod
k run test --image=busybox --dry-run=client -o yaml -- sleep 3600 > pod.yaml

# Generate a Service
k expose deployment web --port=80 --target-port=8080 --dry-run=client -o yaml > svc.yaml

# Generate RBAC resources
k create role pod-reader --verb=get,list --resource=pods --dry-run=client -o yaml
k create rolebinding read-pods --role=pod-reader --serviceaccount=default:my-sa --dry-run=client -o yaml

Edit the generated YAML only for fields you need to change. This minimizes indentation errors and saves 2 to 5 minutes per question compared to writing YAML from scratch.

Use the Documentation Efficiently

You have access to kubernetes.io during the exam. Bookmark these pages before exam day:

• kubectl cheat sheet
• Pod spec reference
• PersistentVolumeClaim examples
• NetworkPolicy examples
• RBAC reference
• kubeadm upgrade documentation
• etcd backup and restore procedures

A fast documentation lookup takes 15 seconds. A slow one takes 2 minutes. Over 15 to 20 questions, that difference adds up to 5 to 10 minutes. Know where things are before you need them.

During the Exam: Common Tasks and How to Handle Them

Troubleshooting Questions (30% of the Exam)

Troubleshooting is the heaviest domain. When you get a "fix this broken cluster" question, follow a systematic debugging flow:

1. kubectl get pods -A and kubectl get nodes for a quick status check
2. kubectl describe <resource> to read events
3. kubectl logs <pod> for container-level errors
4. journalctl -u kubelet for node-level problems
5. Check /etc/kubernetes/manifests/ for static pod issues
6. Verify file permissions and certificate paths

Do not guess. Follow the flow. The symptoms will point you to the problem if you read the output carefully.

etcd Backup and Restore

This shows up on almost every CKA exam. Have the commands memorized:

# Backup
ETCDCTL_API=3 etcdctl snapshot save /path/to/backup.db \
  --endpoints=https://127.0.0.1:2379 \
  --cacert=/etc/kubernetes/pki/etcd/ca.crt \
  --cert=/etc/kubernetes/pki/etcd/server.crt \
  --key=/etc/kubernetes/pki/etcd/server.key

# Restore
ETCDCTL_API=3 etcdctl snapshot restore /path/to/backup.db \
  --data-dir=/var/lib/etcd-restored

After restore, update the etcd static pod manifest to point to the new data directory. This second step is the one people forget.

NetworkPolicy Questions

NetworkPolicies have tricky YAML syntax. The key thing to remember is that once any NetworkPolicy applies to a Pod, all traffic not explicitly allowed is denied.

If the question asks you to allow ingress from specific Pods, you need a NetworkPolicy with a podSelector matching the target Pods and an ingress rule specifying the source.

Use the documentation for the exact YAML structure. This is one of the topics where looking it up is faster and more reliable than writing from memory.

RBAC Questions

RBAC questions are common and usually straightforward. Use imperative commands:

k create role <name> --verb=get,list,watch --resource=pods -n <namespace>
k create rolebinding <name> --role=<role-name> --serviceaccount=<namespace>:<sa-name> -n <namespace>

Verify with:

k auth can-i get pods --as system:serviceaccount:<namespace>:<sa-name> -n <namespace>

The Last 15 Minutes

If you managed your time well, you should have 15 minutes left with only flagged (hard) questions remaining.

Review Pass

Use the last 5 minutes for a quick review of completed questions:

• Did you create resources in the correct namespace?
• Did you switch contexts for each question?
• Are your Pods actually running? (kubectl get pods -n <namespace>)
• Did you save output to the file path specified in the question?

You will not have time to re-solve anything, but you can catch simple errors like wrong namespaces or missing labels. A 30-second fix on a completed question is worth more than spending those 30 seconds on a hard question you are unlikely to solve.

If You Are Running Out of Time

With 5 minutes left and questions unanswered, prioritize by point value. Look at what is worth the most. A 7% question you can partially solve is better than a 4% question you cannot touch.

For questions you cannot fully solve, do what you can. Partial credit is not officially confirmed, but creating the resource with most of the correct configuration is better than leaving the question blank.

After the Exam

When You Get Results

The CKA exam results are not instant. You will receive an email with your score within 24 hours. Most people get results within 12 to 18 hours. Some get them faster.

The waiting is the hardest part. There is nothing you can do to speed it up. Close your laptop and do something else.

Understanding Your Score

Your results email will show:

• Your total score as a percentage
• Whether you passed (66% or above) or failed
• A breakdown by domain showing your performance in each area

The domain breakdown is valuable even if you passed. It shows your strengths and weaknesses for future certifications like the CKAD or CKS.

If You Passed

Congratulations. Here is what to do:

1. Download your certificate. It is available in the Linux Foundation training portal. Download the PDF and save it somewhere permanent.
2. Update LinkedIn. Add the certification with the verification link. This is the first place recruiters check.
3. Update your resume. Add "Certified Kubernetes Administrator (CKA)" to your certifications section.
4. Consider next steps. The CKAD shares 60% to 70% of content with the CKA, so studying for it while your CKA knowledge is fresh is efficient. The CKS requires an active CKA, so you are already eligible. See the certification path guide for the optimal order.

CKA holders earn $130,000 to $180,000 in the US. If you are not in that range, the certification strengthens your position when negotiating a raise or interviewing elsewhere.

If You Failed

You get a free retake. Take a breath.

Look at your domain scores. Identify the weakest areas. If troubleshooting was low, spend a week breaking and fixing clusters. If Services & Networking was the problem, drill NetworkPolicies and Service debugging. If you ran out of time, practice speed with timed mock exercises.

Most people who fail the first attempt pass the retake. The exam experience itself teaches you things that practice cannot fully replicate: the time pressure, the proctoring environment, and the specific way questions are worded.

Schedule your retake 2 to 4 weeks out. That gives you enough time to address your weak areas without losing the knowledge you already have.

The Complete CKA Exam Day Checklist

Print this. Check each item off.

One Week Before

• Second practice session completed (score above 50%)
• ID verified (not expired, name matches registration)
• PSI Secure Browser downloaded and tested
• Desk cleared and exam environment set up
• Webcam and microphone tested
• Documentation bookmarks set up in your browser
• Reviewed weak areas from practice session results

The Night Before

• Desk is clean (nothing except computer, keyboard, mouse)
• Second monitor disconnected or covered
• Phone charger in another room
• Alarm set (give yourself 2 hours before exam time)
• Light review of etcd backup commands and troubleshooting flow
• Stop studying by 9 PM. Sleep matters more than last-minute cramming.

Exam Morning

• Eat a real meal
• Normal caffeine intake (nothing unusual)
• Water bottle nearby (you can drink during the exam)
• Phone in another room, notifications off
• Door closed, housemates notified
• All applications closed except PSI Secure Browser
• ID next to keyboard
• Check in 15 minutes early

First 5 Minutes of Exam

• Set up kubectl alias and autocompletion
• Configure vim settings for YAML
• Skim all questions and note point values
• Identify easy, medium, and hard questions
• Note the time and set mental checkpoints

During the Exam

• Switch context on every question (first action, every time)
• Read full question before starting
• Check for namespace requirements
• Use --dry-run=client -o yaml for resource generation
• Flag and skip questions after 7 to 8 minutes
• Verify resources exist after creating them
• Check time against benchmarks at 90, 60, and 30 minutes

Last 15 Minutes

• Attempt flagged questions by point value
• Review completed questions for namespace and context errors
• Verify Pods are running, not stuck in error states
• Confirm output files are saved to the correct paths

FAQ

What do I need on my desk for the CKA exam?

Your computer (one monitor only), keyboard, mouse, and a valid government-issued photo ID. Nothing else. No phones, notes, pens, books, or second monitors. The proctor will ask you to show your desk via webcam before the exam starts. Clear everything off the surface, including under the desk area.

Can I take a bathroom break during the CKA?

Yes, but the timer does not pause. Every minute away from the screen is a minute lost. Use the restroom before the exam starts. If you must take a break during the exam, be quick. Most people do not take breaks because the time pressure is too tight.

How long do CKA results take?

Results arrive by email within 24 hours. Most people receive them within 12 to 18 hours. Some receive them in as few as 4 to 6 hours. There is no way to check early. The email will contain your score, pass/fail status, and a domain-by-domain breakdown.

What if my internet drops during the CKA exam?

If your connection drops briefly, the proctoring session may reconnect automatically. If it drops for an extended period, you may need to contact PSI support to resume. Using a wired ethernet connection instead of WiFi significantly reduces this risk. If the disconnection was not your fault and caused significant lost time, contact Linux Foundation support to discuss options.

Can I use multiple browser tabs during the CKA?

You can have the exam terminal and the Kubernetes documentation (kubernetes.io) open in separate tabs. You cannot access any other websites, including Stack Overflow, GitHub, personal notes, or blogs. The PSI Secure Browser enforces these restrictions. Having bookmarks set up in advance within the allowed documentation makes lookups much faster.

What score do I need to pass the CKA?

You need 66%. That means you can miss about a third of the exam and still pass. This should inform your strategy: do not spend 15 minutes on a 4% question. Collect the easy and medium points first, then tackle the hard questions. If you pass the practice sessions at 55% or above, you are likely to pass the real exam, which is calibrated to be somewhat easier.

What happens if I fail the CKA exam?

Your purchase includes one free retake. There is no mandatory waiting period, so you can schedule the retake whenever you feel ready. Review your domain score breakdown to identify weak areas, study those areas for 2 to 4 weeks, and then take the retake. Most people who fail the first attempt pass on the second try. Read Is Kubernetes Certification Worth It? for the full perspective on the investment.