The online version of the Linux Foundation Certified Kubernetes Administrator (CKA) Program engine is the most flexible option: it simulates the real test with intelligent functions and places no limit on installation devices, so 85 practice questions travel with you.
Linux Foundation CKA Exam Overview:
| Certification Vendor: | Linux Foundation / Cloud Native Computing Foundation (CNCF) |
|---|---|
| Exam Name: | Certified Kubernetes Administrator (CKA) Program Exam |
| Exam Number: | CKA |
| Related Certifications: | Certified Kubernetes Application Developer (CKAD) Certified Kubernetes Security Specialist (CKS) |
| Available Languages: | Simplified Chinese, English, Japanese |
| Passing Score: | 66% |
| Exam Format: | Online proctored, Command-line tasks, Hands-on in real Kubernetes environment, Performance-based |
| Exam Duration: | 120 minutes |
| Certificate Validity Period: | 2 years |
| Real Exam Qty: | 15-20 performance-based tasks |
| Exam Price: | $445 USD |
| Recommended Training: | Introduction to Kubernetes (Free Course) LFS258: Kubernetes Fundamentals |
| Exam Registration: | Linux Foundation Training Portal |
| Sample Questions: | DOWNLOAD DEMO |
| Exam Way: | Online, remotely proctored via PSI; browser-based terminal environment |
| Pre Condition: | No formal prerequisites; basic Linux and Kubernetes knowledge recommended |
| Official Syllabus URL: | https://training.linuxfoundation.org/certification/certified-kubernetes-administrator-cka/ |
Linux Foundation CKA Exam Syllabus Topics:
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Workloads & Scheduling | 15% | - Pod lifecycle, init containers, probes - Pod scheduling: node selector, affinity, taints/tolerations - Deployments, rolling updates and rollbacks - Resource requests, limits and autoscaling - Configure applications with ConfigMaps and Secrets |
| Topic 2: Services & Networking | 20% | - CNI configuration and troubleshooting - CoreDNS and service discovery - Ingress resources and controllers - Service types: ClusterIP, NodePort, LoadBalancer, ExternalName - Network policies |
| Topic 3: Storage | 10% | - Volume types and access modes - Persistent Volumes (PV) and Persistent Volume Claims (PVC) - StatefulSet storage configuration - StorageClasses and dynamic provisioning |
| Topic 4: Troubleshooting | 30% | - Log collection and analysis - Cluster component health checks - Worker node issues and recovery - Network connectivity and DNS resolution problems - Pod and application failures - Control plane component failures |
| Topic 5: Cluster Architecture, Installation & Configuration | 25% | - Work with CRDs and Operators - Prepare infrastructure for cluster installation - Manage RBAC - Implement high availability control plane - Understand CNI, CSI, CRI interfaces - Install components via Helm / Kustomize - Create and manage clusters with kubeadm - Manage cluster lifecycle and upgrades |
Linux Foundation Certified Kubernetes Administrator (CKA) Program: What Candidates Ask
LFS258: Kubernetes Fundamentals: Visit official page
Introduction to Kubernetes (Free Course): Visit official page
Linux Foundation Training Portal: register for CKA
The package includes 85 practice questions for the CKA exam, all with verified answers. The same content is available in three formats, so you can switch freely.
The CKA exam contains 15-20 performance-based tasks questions to complete within 120 minutes minutes. Rehearsing under the same limit on the simulator builds calm, automatic pacing.
The PDF reads on phones, tablets, and computers, and it prints cleanly for candidates who like marking notes on paper. The PC file is an interactive simulator that makes rehearsal engaging. The online file is the updated edition of the PC version: intelligent functions, real-test simulation, and no limit on installation devices. All three carry the same questions and answers.
No formal prerequisites; basic Linux and Kubernetes knowledge recommended
- Cluster Architecture, Installation & Configuration (25%)
- Workloads & Scheduling (15%)
- Storage (10%)
Plan your hours according to each topic's weight.
CKA requires 66% to pass, and the official exam fee is $445 USD. Fixing both numbers early keeps your practice target and your budget on the same page.
Before you buy, our team answers any question about the Linux Foundation Certified Kubernetes Administrator (CKA) Program material, and the free demo lets you test it. After payment, the files reach your email within seconds, updates follow by email whenever the exam changes, and we protect your personal information throughout. Promotions appear on our homepage from time to time, so regular visitors often buy at a better price.
Linux Foundation Certified Kubernetes Administrator (CKA) Program Sample Questions:
Create a file:
/opt/KUCC00302/kucc00302.txt that lists all pods that implement service baz in namespace development.
The format of the file should be one pod name per line.
Correct Answer:



Ensure a single instance of pod nginx is running on each node of the Kubernetes cluster where nginx also represents the Image name which has to be used. Do not override any taints currently in place.
Use DaemonSet to complete this task and use ds-kusc00201 as DaemonSet name.
Correct Answer:




Score: 5%
Task
From the pod label name=cpu-utilizer, find pods running high CPU workloads and write the name of the pod consuming most CPU to the file /opt/KUTR00401/KUTR00401.txt (which already exists).
Correct Answer:
Solution:
kubectl top -l name=cpu-user -A
echo 'pod name' >> /opt/KUT00401/KUT00401.txt
Score:7%
Context
An existing Pod needs to be integrated into the Kubernetes built-in logging architecture (e. g. kubectl logs).
Adding a streaming sidecar container is a good and common way to accomplish this requirement.
Task
Add a sidecar container named sidecar, using the busybox Image, to the existing Pod big-corp-app. The new sidecar container has to run the following command:
/bin/sh -c tail -n+1 -f /va r/log/big-corp-app.log
Use a Volume, mounted at /var/log, to make the log file big-corp-app.log available to the sidecar container.
Correct Answer:
Solution:
#
kubectl get pod big-corp-app -o yaml
#
apiVersion: v1
kind: Pod
metadata:
name: big-corp-app
spec:
containers:
- name: big-corp-app
image: busybox
args:
- /bin/sh
- -c
- >
i=0;
while true;
do
echo "$(date) INFO $i" >> /var/log/big-corp-app.log;
i=$((i+1));
sleep 1;
done
volumeMounts:
- name: logs
mountPath: /var/log
- name: count-log-1
image: busybox
args: [/bin/sh, -c, 'tail -n+1 -f /var/log/big-corp-app.log']
volumeMounts:
- name: logs
mountPath: /var/log
volumes:
- name: logs
emptyDir: {
}
#
kubectl logs big-corp-app -c count-log-1
You must connect to the correct host.
Failure to do so may result in a zero score.
[candidate@base] $ ssh Cka000037
Context
A legacy app needs to be integrated into the Kubernetes built-in logging architecture (i.e.
kubectl logs). Adding a streaming co-located container is a good and common way to accomplish this requirement.
Task
Update the existing Deployment synergy-leverager, adding a co-located container named sidecar using the busybox:stable image to the existing Pod . The new co-located container has to run the following command:
/bin/sh -c "tail -n+1 -f /var/log/syne
rgy-leverager.log"
Use a Volume mounted at /var/log to make the log file synergy-leverager.log available to the co- located container .
Do not modify the specification of the existing container other than adding the required volume mount .
Failure to do so may result in a reduced score.
Correct Answer:
Task Summary
* SSH into the correct node: cka000037
* Modify existing deployment synergy-leverager
* Add a sidecar container:
* Name: sidecar
* Image: busybox:stable
* Command:
/bin/sh -c "tail -n+1 -f /var/log/synergy-leverager.log"
* Use a shared volume mounted at /var/log
* Don't touch existing container config except adding volume mount
Step-by-Step Solution
1## SSH into the correct node
ssh cka000037
## Skipping this will result in a zero score.
2## Edit the deployment
kubectl edit deployment synergy-leverager
This opens the deployment YAML in your default editor (vi or similar).
3## Modify the spec as follows
# Inside the spec.template.spec, do these 3 things:
# A. Define a shared volume
Add under volumes: (at the same level as containers):
volumes:
- name: log-volume
emptyDir: {}
# B. Add volume mount to the existing container
Locate the existing container under containers: and add this:
volumeMounts:
- name: log-volume
mountPath: /var/log
# Do not change any other configuration for this container.
# C. Add the sidecar container
Still inside containers:, add the new container definition after the first one:
- name: sidecar
image: busybox:stable
command:
- /bin/sh
- -c
- "tail -n+1 -f /var/log/synergy-leverager.log"
volumeMounts:
- name: log-volume
mountPath: /var/log
spec:
containers:
- name: main-container
image: your-existing-image
volumeMounts:
- name: log-volume
mountPath: /var/log
- name: sidecar
image: busybox:stable
command:
- /bin/sh
- -c
- "tail -n+1 -f /var/log/synergy-leverager.log"
volumeMounts:
- name: log-volume
mountPath: /var/log
volumes:
- name: log-volume
emptyDir: {}
Save and exit
If using vi or vim, type:
bash
CopyEdit
wq
5## Verify
Check the updated pods:
kubectl get pods -l app=synergy-leverager
Pick a pod name and describe it:
kubectl describe pod <pod-name>
Confirm:
* 2 containers running (main-container + sidecar)
* Volume mounted at /var/log
ssh cka000037
kubectl edit deployment synergy-leverager
# Modify as explained above
kubectl get pods -l app=synergy-leverager
kubectl describe pod <pod-name>
Viewing page 1 out of 17 pages.
Viewing questions 1-5 out of 85 questions.

1604 Customer Reviews
