This home page is designed like a practical exam-prep article. You can scan the exam format, understand the question structure, study examples and move into live practice without changing context.
The home page now starts with task-based Kubernetes scenarios, not abstract theory.
Each question follows a practical flow: read the task, choose commands, apply YAML and verify.
Read the strategy notes, then jump into timed practice sessions when you are ready.
CKA focuses on administrator responsibilities. CKAD focuses on building, configuring and troubleshooting applications that run on Kubernetes. Both reward fast terminal work and clear command choices.
Read each task, set the correct context and namespace, then solve directly in the terminal.
Use kubectl dry-run output, short names and official docs to reduce YAML typing time.
Verify every result with get, describe, logs, events or a direct workload check before moving on.
A strong CKA or CKAD practice question should look like the real exam: direct task, minimal story, clear constraints and a result you can verify.
A short scenario tells you what Kubernetes resource to create, update, inspect or fix.
The prompt may mention a namespace, cluster context, labels, image, port, storage class or policy rule.
Most answers use kubectl first, then generated YAML when the task needs exact fields.
Every answer should end with a quick check such as get, describe, logs, events or endpoint validation.
In namespace app-team, create a Deployment named apiwith image nginx:1.27 and 2 replicas. Expose it on port 80, then verify that the Service has endpoints.
Both exams are hands-on, but the questions feel different. CKA asks you to operate the cluster. CKAD asks you to build and fix workloads inside the cluster.
Cluster administration
Nodes, scheduling, storage, services, troubleshooting, upgrades and cluster operations.
Application delivery
Pods, Deployments, Jobs, probes, ConfigMaps, Secrets, Services and NetworkPolicy.
Create resources, inspect node health, debug workloads, manage scheduling and read events quickly.
Deploy Pods, Deployments, Jobs, CronJobs, ConfigMaps, Secrets, probes and resource limits.
Expose applications with Services and Ingress, troubleshoot DNS and apply NetworkPolicy rules.
Work with ServiceAccounts, RBAC, securityContext settings, admission behavior and least privilege.
Use this same flow for every mock question. Repetition is what turns Kubernetes lookup into exam speed.
Find the namespace, resource type, name, image, port, labels and expected result.
Use kubectl create or run with dry-run output when a manifest will save time.
Edit only the fields required by the task, then apply the manifest or run the command.
Confirm with get, describe, logs, events, rollout status, endpoints or a direct request.
kubectl create deployment api --image=nginx:1.27 --dry-run=client -o yamlkubectl get events -n app-team --sort-by=.lastTimestampkubectl get endpoints api -n app-teamkubectl logs pod/api-1 -n app-team --previousUse these as short drills. Solve first, reveal mentally, then compare with the answer.
Create a deployment named web with 3 replicas using nginx:1.27, then expose it as a ClusterIP service on port 80.
kubectl create deployment web --image=nginx:1.27 --replicas=3
kubectl expose deployment web --port=80 --target-port=80
kubectl get deploy,svc webVerify the selector and endpoint count. A service without matching endpoints usually means the labels do not line up.
Update an existing pod manifest so the app is ready only after /healthz returns success on container port 8080.
readinessProbe:
httpGet:
path: /healthz
port: 8080
initialDelaySeconds: 5
periodSeconds: 10Use a readiness probe when traffic should wait. Use a liveness probe when Kubernetes should restart a stuck container.
A pod in namespace payments is CrashLoopBackOff. Find the error and capture the previous container logs.
kubectl get pods -n payments
kubectl describe pod <pod-name> -n payments
kubectl logs <pod-name> -n payments --previousIn the exam, describe output and events often point to image, command, probe or volume issues faster than guessing.
Allow only pods with label role=frontend to connect to pods labeled app=api on TCP port 8080 in the same namespace.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: allow-frontend-to-api
spec:
podSelector:
matchLabels:
app: api
ingress:
- from:
- podSelector:
matchLabels:
role: frontend
ports:
- protocol: TCP
port: 8080
policyTypes:
- IngressNetworkPolicies are namespace-scoped. If cross-namespace access is required, include a namespaceSelector.
Build a habit of reading the noun, namespace and success condition before touching the terminal.
Dry-run output, explain, rollout status, events and logs are the daily tools of exam speed.
Selectors, probe ports, command arrays and indentation cause more lost minutes than hard concepts.