CKA Practice Test 6 — 10 Questions

Question 1

A pod is stuck in Pending state. Running 'kubectl describe pod mypod' reveals the event '0/4 nodes are available: 3 Insufficient memory, 1 node(s) had taints that the pod didn't tolerate'. What is the most likely cause?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The pod requests more memory than available on any node and does not tolerate a node taint. The pod is pending because no node can satisfy its resource requirements or tolerate the node taints. The event indicates insufficient memory and a taint issue. The correct answer is that the pod requests more memory than any node can allocate and also does not tolerate a node taint.

Answer

The kubelet on all nodes is not running

Answer

The pod's container image is not pullable

Answer

The pod is using a hostPort that conflicts with an existing pod

Question 2

A pod uses a PVC with access mode RWO. The pod is scheduled on node A. You want to schedule another pod on node B that uses the same PVC. What will happen?

Accepted Answer

The second pod will be stuck in ContainerCreating state until the first pod releases the volume. A PVC with access mode RWO (ReadWriteOnce) can only be mounted as a block device or filesystem by a single node at a time. When the first pod on node A has the volume attached, the second pod on node B cannot attach the same volume because the underlying storage (e.g., an AWS EBS volume or GCE Persistent Disk) does not support multi-node attachment. The second pod will remain in ContainerCreating state with a 'Multi-Attach error' until the first pod releases the volume (e.g., by being deleted or rescheduled).

Answer

Both pods will mount the volume and share it without issues

Answer

The second pod will successfully mount the volume as read-only

Answer

The first pod will be evicted to allow the second pod to use the volume

Question 3

Which command shows resource usage (CPU/memory) of all pods in the default namespace?

Accepted Answer

kubectl top pods. kubectl top pod shows CPU and memory metrics for pods.

Answer

kubectl describe pods

Answer

kubectl logs pods

Answer

kubectl get pods -o wide

Question 4

During a 'kubeadm init', the administrator sees the message 'Your Kubernetes control-plane has been initialized successfully!' but the 'kubectl get nodes' shows the control plane node as 'NotReady'. What is the most likely missing step?

Accepted Answer

Install a CNI plugin such as Calico or Flannel.. The 'NotReady' status indicates that the kubelet on the control plane node is running but cannot report readiness because the node's network is not configured. A CNI plugin (e.g., Calico, Flannel, Weave) must be installed to set up the pod network, which is required for the kubelet to register the node as 'Ready'. Without a CNI plugin, the node's network conditions remain unmet, and the control plane cannot function properly.

Answer

Generate a join token for worker nodes.

Answer

Copy the kubeconfig to the user's home directory.

Answer

Check that the kubelet is running on the control plane node.

Question 5

A node in your cluster is marked as NotReady. You SSH into the node and run 'systemctl status kubelet'. The output shows the kubelet is inactive (dead). What should you do FIRST to restore the node?

Accepted Answer

Run 'systemctl start kubelet'. The kubelet service is stopped. The first step is to start it with 'systemctl start kubelet'. If it fails to start, further investigation with journalctl is needed.

Answer

Reboot the node

Answer

Delete the node object from the cluster

Answer

Reinstall the kubelet package

Question 6

You run 'kubectl get nodes' and one node shows 'NotReady'. Which command should you run first to check the kubelet status on that node?

Accepted Answer

journalctl -u kubelet. The kubelet is responsible for node status. On the node, you can check its logs with journalctl.

Answer

kubectl describe node <node-name>

Answer

cat /var/log/syslog | grep kubelet

Answer

systemctl status kube-apiserver

Question 7

Which command lists all events in the cluster sorted by timestamp?

Accepted Answer

kubectl get events --sort-by=.metadata.creationTimestamp. 'kubectl get events --sort-by=.metadata.creationTimestamp' shows events sorted by creation time. Alternatively, 'kubectl get events -w' watches events but does not sort.

Answer

kubectl get events --watch

Answer

kubectl logs --events

Answer

kubectl describe events

Question 8

You run 'kubectl get pods' and see a pod in 'CrashLoopBackOff'. What command would you run to see the reason for the crash?

Accepted Answer

kubectl describe pod . B is correct because `kubectl describe pod ` provides detailed information about the pod, including the container state, restart count, and the last termination reason (e.g., 'Error' or 'OOMKilled') along with its exit code. To view the actual stdout/stderr logs of the crashed container, you would use `kubectl logs --previous`.

Answer

kubectl top pod <pod-name>

Answer

kubectl rollout status deployment <deployment-name>

Answer

kubectl get events --field-selector involvedObject.name=<pod-name>

Question 9

You have a Deployment with livenessProbe configured. The pod restarts every few minutes. 'kubectl describe pod' shows the liveness probe is failing with 'HTTP probe failed with statuscode: 503'. The application's /healthz endpoint returns 200 from within the pod using 'kubectl exec'. What could be the issue?

Accepted Answer

The livenessProbe is configured with the wrong port. The liveness probe is failing externally but the endpoint works internally. This suggests the probe is hitting the wrong port or the network path is different. The most likely cause is that the livenessProbe is configured with a wrong port number.

Answer

The readinessProbe is interfering with the livenessProbe

Answer

The application has a memory leak

Answer

The kubelet on the node is misconfigured

Question 10

You need to upgrade a Kubernetes cluster from v1.28 to v1.29 using kubeadm. After upgrading the control plane, what should you do on each worker node?

Accepted Answer

kubectl drain ; kubeadm upgrade node; kubectl uncordon . The standard kubeadm upgrade workflow for worker nodes requires first draining the node to safely evict all pods, then running 'kubeadm upgrade node' to upgrade the kubelet and kube-proxy configuration, and finally uncordoning the node to make it schedulable again. This sequence ensures minimal disruption to workloads and follows the official Kubernetes upgrade documentation.

Answer

kubeadm upgrade node config --kubelet-version v1.29.0

Answer

kubectl delete node <node>; kubeadm upgrade node

Answer

kubeadm upgrade node; kubectl uncordon <node>