Google Exam Professional Cloud DevOps Engineer Topic 1 Question 87 Discussion

Actual exam question for Google's Professional Cloud DevOps Engineer exam

Question #: 87
Topic #: 1

[All Professional Cloud DevOps Engineer Questions]

You have a set of applications running on a Google Kubernetes Engine (GKE) cluster, and you are using Stackdriver Kubernetes Engine Monitoring. You are bringing a new containerized application required by your company into production. This application is written by a third party and cannot be modified or reconfigured. The application writes its log information to /var/log/app_messages.log, and you want to send these log entries to Stackdriver Logging. What should you do?

AUse the default Stackdriver Kubernetes Engine Monitoring agent configuration.

BDeploy a Fluentd daemonset to GKE. Then create a customized input and output configuration to tail the log file in the application's pods and write to Slackdriver Logging.

CInstall Kubernetes on Google Compute Engine (GCE> and redeploy your applications. Then customize the built-in Stackdriver Logging configuration to tail the log file in the application's pods and write to Stackdriver Logging.

DWrite a script to tail the log file within the pod and write entries to standard output. Run the script as a sidecar container with the application's pod. Configure a shared volume between the containers to allow the script to have read access to /var/log in the application container.

Show Suggested Answer

Suggested Answer: B, D

by Corazon at Feb 08, 2025, 01:13 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud DevOps Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Noel

9 days ago

Hmm, the default Stackdriver Kubernetes Engine Monitoring agent configuration doesn't seem to be the right solution here. We need to do some custom configuration to get the logs into Stackdriver Logging.

upvoted 0 times

...

Stefania

13 days ago

I'm not sure, but I think option D could also work. Writing a script to tail the log file within the pod and configuring a shared volume seems like a feasible approach. It might require more manual setup, but it could be a good alternative.

upvoted 0 times

...

Vallie

17 days ago

I agree with Nobuko. Option B provides a clear solution without needing to redeploy applications or write custom scripts. It's the most efficient way to handle the log information.

upvoted 0 times

...

Nobuko

25 days ago

I think option B is the best choice. Deploying a Fluentd daemonset and creating a customized configuration seems like the most direct way to send the log entries to Stackdriver Logging.

upvoted 0 times

...