Certified Kubernetes Administrator Free Practice Questions
This practice bank exercises foundational CKA knowledge: control plane components (controller manager, kube-proxy, scheduler), scheduling constraints (node affinity), kubectl commands for context, events, logs, and node details, service networking (ClusterIP), persistent storage (PVC, StorageObjectInUseProtection), resource limits, readiness probes, deployment strategies (RollingUpdate), security contexts, and namespaces. Decisions involve choosing the correct commands, understanding core concepts, and applying Kubernetes primitives to manage clusters, schedule pods, configure storage, and troubleshoot issues. The set reinforces exam-relevant topics without claiming to cover the full blueprint.
What this CKA practice set measures
This is an analysis of the practice bank, not a claim about the vendor's live exam blueprint. Use it to identify the knowledge, judgment, and recall patterns exercised here, then verify your coverage against the current official exam guide.
Control Plane and Cluster State
The control plane components are critical for maintaining cluster state. The controller manager runs reconciliation loops to drive actual state toward desired state. kube-proxy maintains network rules on nodes. The scheduler assigns pods to nodes. Admission controllers like StorageObjectInUseProtection validate and protect resources. Understanding their roles helps in diagnosing cluster issues and configuring proper behavior.
- Controller manager is responsible for maintaining desired cluster state through control loops.
- kube-proxy enables network communication by managing iptables or IPVS rules on each node.
- StorageObjectInUseProtection prevents removal of PersistentVolumes still bound to PVCs.
Scheduling and Workload Management
Pod placement and workload updates are key CKA skills. Node affinity constrains pods to nodes with specific labels. RollingUpdate strategy ensures zero-downtime deployments. Resource limits cap CPU and memory usage. Readiness probes determine service traffic eligibility. These concepts help maintain application availability and efficient resource usage.
- Node affinity schedules pods on nodes matching label selectors.
- RollingUpdate gradually replaces pods to avoid downtime during updates.
- Setting resources.limits.cpu caps maximum CPU consumption per container.
Networking and Storage
Networking and storage are core infrastructure topics. ClusterIP Services expose applications internally only. PersistentVolumeClaims request storage with specific access modes. StorageClass defines dynamic provisioning. Taints and tolerations (mentioned in hints) complement affinity for advanced scheduling. Mastery of these resources enables reliable multi-tier applications.
- ClusterIP Services provide internal cluster-wide IP for pod-to-pod communication.
- PersistentVolumeClaims specify size and access modes for storage requests.
- StorageClass defines the provisioner and parameters for dynamic volume creation.
Troubleshooting and Administration
Efficient troubleshooting requires knowledge of kubectl commands. kubectl get events --sort-by shows cluster events chronologically. kubectl logs --previous retrieves logs from crashed containers. kubectl describe node gives detailed node status. Current context is obtained via kubectl config current-context. These commands diagnose pod failures, node issues, and configuration mistakes.
- kubectl get events --sort-by='.metadata.creationTimestamp' lists events in time order.
- kubectl logs --previous shows logs from the last terminated container instance.
- kubectl describe node displays node conditions, addresses, and resource usage.
Practice Certified Kubernetes Administrator with real flashcards
Read the prompt, commit to an answer, then flip the card. Move through the deck at your own pace and repeat any topic that does not come back quickly.
Card 1 of 20
1 reviewed this session
Static practice bank
Start the 15-question diagnostic
The complete question bank is embedded in this pre-rendered page. There is no database request or second content download when you begin.
Which component of Kubernetes is primarily responsible for maintaining the desired state of the cluster?
Show hint
Understand the control plane components and their responsibilities.
Study workflow
Turn one CKA attempt into a study plan
- 1
Inspect Current Context
Run `kubectl config current-context` to verify which cluster you are targeting. This is essential before performing any operations to avoid unintended changes.
- 2
Troubleshoot CrashLoopBackOff
Use `kubectl logs --previous <pod-name>` to see logs from the crashed container. Then check pod events with `kubectl describe pod <pod-name>` for reasons like image pull errors or liveness probe failures.
- 3
Apply CPU Limits
In a Pod spec, under `spec.containers[].resources.limits.cpu`, specify the maximum CPU. Also set requests for guaranteed scheduling. Use units like `500m` for half a core.
- 4
Create a PersistentVolumeClaim
Define a PVC YAML with `accessModes` (e.g., ReadWriteOnce) and `resources.requests.storage`. Then reference it in a pod's `volumes` and `volumeMounts` to mount storage dynamically.
- 5
Rollback a Deployment
If a rollout causes issues, run `kubectl rollout undo deployment/<name>` to revert to the previous revision. Check rollout history with `kubectl rollout history deployment/<name>`.
FAQ
Questions about this CKA practice page
Clear boundaries on what the bank covers, how to use it, and where official vendor information still matters.
What is the difference between liveness and readiness probes?+
Liveness probes restart a container if it fails, indicating the application is deadlocked or unhealthy. Readiness probes determine if a pod should receive traffic; if it fails, the pod is removed from Service endpoints but not restarted.
How do taints and tolerations complement node affinity?+
Taints repel pods from nodes unless they have matching tolerations. Node affinity attracts pods to nodes. Together they allow fine-grained control: you can ensure pods only run on dedicated nodes by tainting them and adding tolerations to specific pods.
What is the role of kube-proxy in CKA?+
kube-proxy runs on each node and implements the Service abstraction by maintaining network rules (iptables/IPVS). It forwards traffic to healthy pods and supports load balancing across pods. It is not responsible for scheduling.
How does RollingUpdate achieve zero downtime?+
RollingUpdate replaces old pods one by one with new versions while ensuring the number of available pods never drops below a configurable threshold (e.g., `maxUnavailable` and `maxSurge`). This allows the application to serve traffic continuously during the update.
What admission controller validates PersistentVolume usage?+
StorageObjectInUseProtection ensures that PersistentVolumeClaims and PersistentVolumes in use are not deleted prematurely. It is an admission controller that prevents removal when a pod is still mounted to the volume, protecting data integrity.
Build the next review session
Browse another free bank or use the study strategy guide to turn your misses into spaced review.