You deployed a new container to your GKE cluster, but the application is not responding. You run `kubectl get pods` and see that the Pod status is 'CrashLoopBackOff'.

What is the MOST appropriate next command to diagnose why the container is crashing?

Answer options:

kubectl describe pod [POD_NAME]

kubectl logs [POD_NAME]

kubectl exec -it [POD_NAME] -- /bin/bash

gcloud container clusters describe [CLUSTER_NAME]

How to approach this question

Identify the kubectl command used to view application standard output.

Full Answer

B.kubectl logs [POD_NAME]✓ Correct

When a Pod is in `CrashLoopBackOff`, it means the container starts, crashes, and Kubernetes restarts it. To find out *why* the application code is crashing, you need to view the application's standard output and standard error using `kubectl logs`.

Common mistakes

Trying to `kubectl exec` into a crashing pod. The shell will immediately disconnect when the container crashes.

Question 32 All questions Question 34

Practice the full GCP Associate Cloud Engineer Practice Exam 2

50 questions · hints · full answers · grading

More questions from this exam

Q01Your company is migrating to Google Cloud and needs to establish a resource hierarchy. You have t...Easy Q02You are managing access to a GCP project. You need to grant 15 developers the ability to view Com...Medium Q03You have created a new GCP project using the Cloud Console. You want to deploy a Cloud Function u...Easy Q04Your startup has a strict monthly cloud budget of $500. You want to be notified immediately if yo...Easy Q05Your finance team wants to perform complex SQL analysis on your GCP billing data to understand co...Medium

View all 50 questions →