CKA — Exam Tips & Strategies
The 3-Pass Strategy
Time management is critical in the CKA exam. Use this three-pass approach:
Pass 1 — Quick Wins (First 40 Minutes)
- Scan all questions and identify easy ones (simple resource creation, commands you know)
- Complete every question you can solve in under 3 minutes
- Skip anything that requires significant troubleshooting or lengthy YAML
- Target: Complete 8–10 quick questions
Pass 2 — Medium Tasks (Next 50 Minutes)
- Return to medium-difficulty questions (multi-step tasks, moderate YAML)
- Allocate 5–7 minutes per task
- If you get stuck after 5 minutes, flag it and move on
- Target: Complete 5–7 medium questions
Pass 3 — Hard Tasks (Final 30 Minutes)
- Tackle remaining hard questions (complex troubleshooting, multi-component tasks)
- Even partial answers earn partial credit — always attempt something
- Use the last 5 minutes to review flagged questions
- Target: Attempt all remaining questions
vi/vim Editor Shortcuts
You will use vi or vim to edit YAML files during the exam. Master these shortcuts:
| Shortcut | Action |
|---|---|
i |
Enter insert mode |
Esc |
Exit insert mode |
:wq |
Save and quit |
:q! |
Quit without saving |
dd |
Delete current line |
5dd |
Delete 5 lines |
yy |
Copy (yank) current line |
p |
Paste below |
u |
Undo |
Ctrl + r |
Redo |
/search |
Search forward |
n |
Next search result |
:set number |
Show line numbers |
:set paste |
Enable paste mode (preserves indentation) |
gg |
Go to first line |
G |
Go to last line |
:%d |
Delete all lines |
Exam tip: Before pasting YAML into vim, always run :set paste first. This prevents auto-indentation from breaking your YAML structure.
YAML Best Practices
Indentation Matters
YAML uses spaces, not tabs. In vim, set up:
# Add to your .vimrc or run in vim command mode
:set expandtab
:set tabstop=2
:set shiftwidth=2
Generate, Don’t Write From Scratch
# Generate YAML scaffolds with dry-run
kubectl run nginx --image=nginx --dry-run=client -o yaml > pod.yaml
# Edit only what you need
vim pod.yaml
Common YAML Mistakes
| Mistake | Fix |
|---|---|
| Tabs instead of spaces | Use :set expandtab in vim |
| Wrong indentation level | Check parent-child alignment |
Missing - for list items |
Lists of containers, volumes, ports need - prefix |
Wrong apiVersion |
Check the docs: kubectl api-resources |
| Typo in key names | Use tab-completion or copy from docs |
Common Exam Traps
1. Wrong Cluster Context
Every question specifies a context. If you forget to switch, you create resources on the wrong cluster and lose marks.
Fix: Always run kubectl config use-context <name> as your first command for every question.
2. Wrong Namespace
Some questions specify a namespace. If you create resources in the default namespace, you lose marks.
Fix: Read the question carefully. Set the namespace: kubectl config set-context --current --namespace=<ns>
3. Not Verifying Your Work
Creating a resource does not mean it is correct. Verify before moving on.
Fix: Always verify: kubectl get, kubectl describe, kubectl logs
4. Spending Too Long on One Question
Getting stuck on a 3-point question for 15 minutes means you lose time for easier questions.
Fix: Use the 3-pass strategy. Skip and return.
5. Forgetting etcd Certificate Flags
The etcdctl backup command requires --cacert, --cert, --key, and --endpoints. Missing any one fails the backup.
Fix: Practice the full command until you can type it from memory.
Exam Day Checklist
1 Hour Before
- Close all unnecessary applications
- Clear your desk
- Test webcam and microphone
- Have government ID ready
- Get water (if allowed in your testing area)
- Use the restroom
First 2 Minutes of Exam
- Set up aliases:
alias k=kubectl - Set up exports:
export do="--dry-run=client -o yaml" - Set up tab-completion:
complete -o default -F __start_kubectl k - Verify vim settings:
:set expandtab tabstop=2 shiftwidth=2
During the Exam
- Switch context for every question
- Read the full question before starting
- Verify your work after each task
- Flag hard questions and come back
- Use imperative commands for speed
- Copy YAML snippets from kubernetes.io/docs
Next: Test your foundation knowledge with Practice Questions →