Exam Associate Cloud Engineer topic 1 question 72 discussion

It's C - https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/#debugging-pods

Answer is C - You can't view logs of a pod that isn't deployed, so D is incorrect. C allows you to check the pod deployment messages and look for errors

C is correct, as its help you to check the error

Answer C. Review details of myapp-deployment-58ddbbb995-lp86m Pod and check for warning messages. To find out why a pod is stuck in pending status, you can review the details of the pod and check for any warning messages. Answer C is the correct answer because it suggests reviewing the details of the specific pod that is stuck in pending status. You can use the kubectl describe pod <pod-name> command to view detailed information about the pod, including any warning messages that might indicate why the pod is not scheduled.

D : we first check logs

I vote C; because if we imagine that we will go to a main menu that display the errors of the all deployment object as hole, we will surely navigate thin to the pod menu ! so the C option will direct take us to the second menu.

C is correct, Debugging Pods The first step in debugging a Pod is taking a look at it. Check the current state of the Pod and recent events with the following command: kubectl describe pods ${POD_NAME}

Definitely

I guess it's B. its deployment that creates the pod and it has the information why it is not able to create. it shows the information if you describe the deployment ( kubectl describe deployment )

Answer is C

Answer is C

C is right

Go for C

C is the correct answer: The first step in debugging a Pod is taking a look at it. Check the current state of the Pod and recent events with the following command: kubectl describe pods ${POD_NAME} https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/

C is the correct answer. If a Pod is stuck in Pending it means that it can not be scheduled onto a node. Generally this is because there are insufficient resources of one type or another that prevent scheduling. Look at the output of the kubectl describe ... command above. There should be messages from the scheduler about why it can not schedule your Pod. https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/

C. Review details of myapp-deployment-58ddbbb995-lp86m Pod and check for warning messages.

C. Review details of myapp-deployment-58ddbbb995-lp86m Pod and check for warning messages.