Troubleshooting KCNA Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   Which action best represents the 'isolate' step in a systematic troubleshooting approach for a Kubernetes issue?

   • AReview the cluster's backup and disaster recovery plan
   • BApply a fix directly to the suspected component
   • CDelete all pods in the namespace to reset the environment
   • DNarrow down the issue to a specific component, such as a pod, node, or network policy
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   A pod is running but the application inside is not responding to requests from other services. You have verified that the pod's IP is reachable from within the cluster. What should you check next to diagnose the connectivity issue?

   • ACheck the kubelet logs on the node where the pod is running.
   • BCheck the pod's logs to see if the application is crashing.
   • CCheck the cluster's DNS configuration to ensure the Service name resolves.
   • DCheck the Service's selector and the pod's labels to ensure they match.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Which kubectl command validates a resource definition against the Kubernetes API without actually creating the resource?

   • Akubectl explain <resource>
   • Bkubectl create -f <file>
   • Ckubectl apply --dry-run=client -f <file>
   • Dkubectl get -f <file>
   Reveal Solution Discussion Select an answer first
5. 14foundation · easy

   A service is not reachable from within the cluster. Which command would you use to check the service's endpoints?

   • Akubectl get endpoints <service-name>
   • Bkubectl logs <service-name>
   • Ckubectl get pods -o wide
   • Dkubectl describe node
   Reveal Solution Discussion Select an answer first
6. 15expert · medium

   A pod is in a CrashLoopBackOff state. You have checked the logs and they show a configuration error. You have corrected the configuration in the Deployment manifest and applied it. However, the pod is still crashing. What is the most likely reason?

   • AThe Deployment's rollout strategy is set to Recreate, and the old pod is still running.
   • BThe pod is using a cached image that still contains the old configuration.
   • CThe ConfigMap or Secret referenced by the Deployment has not been updated.
   • DThe liveness probe is failing because the application is not ready.
   Reveal Solution Discussion Select an answer first