Exam Professional Cloud Developer topic 1 question 291 discussion

Actual exam question from Google's Professional Cloud Developer

Question #: 291
Topic #: 1

[All Professional Cloud Developer Questions]

You are currently pushing container images to Artifact Registry and deploying a containerized microservices application to GKE. After deploying the application, you notice that the services do not behave as expected. You use the kubectl get pods command to inspect the state of the application Pods, and discover that one of the Pods has a state of CrashLoopBackoff. How should you troubleshoot the Pod?

A. Connect to the problematic Pod by running the kubectl exec -it POD_NAME - /bin/bash command where the POD_NAME parameter is the name of the problematic Pod. Inspect the logs in the /var/log/messages folder to determine the root cause.
B. Execute the gcloud projects get-iam-policy PROJECT_ID command where the PROJECT_ID parameter is the name of the project where your Artifact Registry resides. Inspect the IAM bindings of the node pool s service account. Validate if the service account has the roles/artifactregistry.reader role.
C. Run the kubectl logs POD_NAME command where the POD_NAME parameter is the name of the problematic Pod. Analyze the logs of the Pod from previous runs to determine the root cause of failed start attempts of the Pod.
D. In the Google Cloud console, navigate to Cloud Logging in the project of the cluster’s VPC. Enter a filter to show denied egress traffic to the Private Google Access CIDR range. Validate if egress traffic is denied from your GKE cluster to the Private Google Access CIDR range.

Show Suggested Answer

Suggested Answer: C 🗳️

by anshad666 at Oct. 12, 2024, 5:05 a.m.

Comments

Submit Cancel

yokoyan

3 weeks, 2 days ago

Selected Answer: C

https://cloud.google.com/kubernetes-engine/docs/troubleshooting/deployed-workloads?hl=ja#CrashLoopBackOff

upvoted 1 times

...

saratk1984

1 month, 2 weeks ago

Selected Answer: C

Why Option C is Correct: • kubectl logs POD_NAME is the standard command to retrieve the stdout/stderr logs from a Pod. • You can add --previous to see logs from the previous container instance that crashed, which is especially helpful in CrashLoopBackOff situations. • These logs are often the fastest way to identify root cause errors such as missing dependencies, configuration issues, or environment variables.

upvoted 1 times

...

anshad666

6 months, 3 weeks ago

Selected Answer: C

container in crashloopbackoff , check logs first

upvoted 2 times

...

Exam Professional Cloud Developer All Questions

View all questions & answers for the Professional Cloud Developer exam

Exam Professional Cloud Developer topic 1 question 291 discussion

Comments

yokoyan

saratk1984

anshad666

SY0-701