Exam Professional Cloud Architect topic 1 question 69 discussion

think answer is B. C cannot be, you don't need to connect to the container to view logs, you connect to stackdriver for this

B is correct. Serial console doesnt give you StdOut

B. Review the Stackdriver logs for the specific GKE container that is serving the unresponsive part of the application. GKE be default integrats with Google Operation Suit (Stackdriver) and you can filter the logs for more specific part of application i.e container to view logs. Also it is most efficient way of investigation.

B is the simples option and more effective

B. Review the Stackdriver logs for the specific GKE container that is serving the unresponsive part of the application. Since the application writes logs to standard output, the logs should be available in the Stackdriver logs for the container running the unresponsive part of the application. Kubernetes Engine automatically exports these logs to Stackdriver, so you can use the Stackdriver Logging console to view the logs. Option A is not the best choice because reviewing the logs for each Compute Engine instance would be time-consuming and may not provide the necessary information. Option C may work, but it involves extra steps and may not be necessary if the logs are available in Stackdriver. Option D is not relevant in this case because Serial Port logs are not likely to provide useful information for troubleshooting an unresponsive web application.

C. Connect to the cluster using gcloud credentials and connect to a container in one of the pods to read the logs. To inspect the logs of a Kubernetes Engine (GKE) cluster to find the cause of an issue, you can connect to the cluster using gcloud credentials and connect to a container in one of the pods to read the logs. This will allow you to access the logs of the application as it is running in the cluster, which should help you identify the cause of the issue.

This should be easy, the answer is B. Just eliminate the wrong answers (A) is not correct because the question is about GKE and not CE. C and D are totally lost

A, C, D all sounds unfeasible (credentials, and compute engine)

B is ok

is correct answer

correct

B is correct ans.I agree. https://cloud.google.com/blog/ja/products/management-tools/finding-your-gke-logs

Go for B

B is the correct answer

B – Review Stackdriver logs for specific GKE container that is serving the unresponsive part of the app. This is a most directly matching answer for this Q, since it reviews GKE container logs, by that advertising this Stackdriver feature. “For container and system logs, GKE deploys a per-node logging agent that reads container logs, adds helpful metadata, and then stores them. The logging agent checks for container logs in the following sources: • Standard output and standard error logs from containerized processes • kubelet and container runtime logs • Logs for system components, such as VM startup scripts” Originally we thought, that D is a right answer, since were confused with 2 seconds restart. But, that’s restart for Pod, not for Node (GCE) D – Review Serial Port logs for each Compute Engince instance, that is serving as the in the cluster. Serial Port output is standard feature of Compute Engine (which retains 1 MB most recent logs for analysis). But, it is irrelevant for Pod’s restart, caused by malfunction of some container.

Answer is B

B is right answer. There is a catch here - Legacy logging of GKE with Stackdriver has deprecated. If this is used, you need to migrate to Cloud Operations for GKE, a new enhanced offering by Google with same functionality. Future questions will have the answer choices with new tool "Cloud Operations for GKE" instead of Stackdriver. https://cloud.google.com/monitoring/kubernetes-engine/legacy-stackdriver/logging