Troubleshooting KCNA Practice Questions (Page 1)

Questions 1–5

1. 1application · easy

   You are writing a new Kubernetes Deployment manifest. You are unsure about the correct field names for resource requests and limits. Which command would help you understand the schema?

   • A`kubectl apply --dry-run=client -f deployment.yaml`
   • B`kubectl explain deployment.spec.template.spec.containers.resources`
   • C`kubectl describe deployment`
   • D`kubectl get deployment -o yaml`
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   Which command displays the logs of a specific container in a pod?

   • Akubectl logs <pod-name> -c <container-name>
   • Bkubectl exec <pod-name> -- logs
   • Ckubectl describe pod <pod-name>
   • Dkubectl get pod <pod-name> -o yaml
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Pods are failing to schedule on a node, and the events show 'Insufficient memory'. What is the most likely cause?

   • AThe node has reached its memory capacity and cannot accommodate the pod's request
   • BThe pod's image pull policy is set to Always
   • CThe node is tainted with a NoSchedule taint
   • DThe pod has a liveness probe that is failing
   Reveal Solution Discussion Select an answer first
5. 4application · medium

   Users report that a web application is intermittently slow. You notice that one of the three replicas is frequently restarting. You check `kubectl describe pod` and see that the container has been OOMKilled multiple times. What is the most likely cause and what should you do?

   • AThe pod is failing its liveness probe; you should adjust the probe settings.
   • BThe node is running out of disk space; you should clean up unused images.
   • CThe pod is exceeding its memory limit; you should increase the memory limit in the Deployment's resource requests/limits.
   • DThe pod is experiencing a network issue; you should check the Service configuration.
   Reveal Solution Discussion Select an answer first
6. 5expert · medium

   A pod is in a Running state but the application is not responding to requests. You have verified that the pod's IP is reachable from within the cluster, and the Service's endpoints include the pod. What should you check next?

   • ACheck the kube-proxy configuration on the node.
   • BCheck the Service's type and ensure it is a LoadBalancer.
   • CCheck the application's logs to see if it is listening on the correct port and if there are any errors.
   • DCheck the node's resource usage and consider moving the pod to another node.
   Reveal Solution Discussion Select an answer first