Blueprint anchor: Exam Foundation / Final Review

Exam objective

Understand the current exam format and blueprint.

What you must be able to do

• Performance-based, command-line exam: solve Kubernetes administration tasks rather than choose MCQ answers.
• Current Linux Foundation exam environment is Kubernetes v1.35 and follows new competencies introduced in February 2025.
• Two hours; current passing score is 66%.
• Official domains: Cluster 25%, Workloads 15%, Networking 20%, Storage 10%, Troubleshooting 30%.
• The number of live exam tasks is not a stable published blueprint item; train for weighted work under time pressure rather than memorizing a task count.

Exam mental model

READ TASK
   ↓
CONTEXT + NAMESPACE
   ↓
CURRENT STATE
   ↓
SMALLEST CORRECT CHANGE
   ↓
VERIFY REQUESTED STATE

Commands / code pattern

kubectl version --client
kubectl config get-contexts
kubectl cluster-info

Verification discipline

After every mutating step, run the smallest command that proves the required outcome. A command returning exit code 0 is not sufficient if the object is still Pending, unready, unbound, unauthorized, or unroutable.

Common exam traps

• Acting in the wrong context or namespace.
• Fixing a symptom without reading events/status first.
• Creating extra resources that the task did not request.
• Forgetting to verify the exact requested final state.
• Spending too long memorizing syntax that kubectl explain or allowed documentation can provide quickly.

Self-guided practice

1. Reproduce the command pattern in a disposable cluster.
2. Change names, namespaces, ports, labels, or constraints so you cannot memorize one answer.
3. Break one field intentionally.
4. Diagnose it using status/events/logs rather than comparing blindly to the solution.
5. Record your time to verified state.

Quick knowledge check

Explain aloud what each command above proves, what it does not prove, and which command you would run next if verification failed.