Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location
Mob_nav_barsMENU

Google Professional Cloud DevOps Engineer Exam - 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?

Show Suggested Answer Hide 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:

0/2000 characters
Submit Cancel
Leanora
6 days ago
I think D could work too, but it seems a bit complex.
upvoted 0 times
...
Dalene
12 days ago
B is the way to go for custom logging!
upvoted 0 times
...
Kris
17 days ago
Option C seems off to me since it suggests using GCE instead of GKE, which we learned isn’t necessary for this scenario.
upvoted 0 times
...
Georgeanna
23 days ago
I feel like the default agent in option A wouldn’t capture custom logs like this one, but I can't recall the details of why that is.
upvoted 0 times
...
Dorinda
28 days ago
I remember something about using sidecar containers from a practice question, so option D might be the right approach, but I’m not confident about the shared volume part.
upvoted 0 times
...
Adelle
1 month ago
I think option B sounds familiar because we practiced deploying Fluentd in our labs, but I'm not entirely sure about the specifics of the configuration.
upvoted 0 times
...
Brinda
1 month ago
This question is testing our understanding of Kubernetes logging and monitoring. I'd start by reviewing the Stackdriver Kubernetes Engine Monitoring documentation to see if there are any built-in options I'm missing, but ultimately I think option B with Fluentd is the most robust solution.
upvoted 0 times
...
Kaitlyn
1 month ago
I think option B is the way to go here. Fluentd is a well-established solution for log forwarding in Kubernetes, and it should be able to handle this scenario without too much trouble.
upvoted 0 times
...
Sherly
1 month ago
Option D looks interesting, using a sidecar container to tail the logs. That could be a good approach if I'm not comfortable with Fluentd. I'll need to think through the implementation details, though.
upvoted 0 times
...
Tom
1 month ago
Hmm, I'm a bit unsure about this one. I'm not very familiar with Fluentd, so I'd need to do some research on how to properly configure it for this use case.
upvoted 0 times
...
Mabelle
1 month ago
This seems like a straightforward question. I'd go with option B and deploy a Fluentd daemonset to handle the log forwarding.
upvoted 0 times
...
Noah
6 months ago
Stackdriver Logging, huh? Sounds like a service that's about as reliable as a stack of drunk toddlers.
upvoted 0 times
...
Simona
6 months ago
Writing a script to tail the log file and run it as a sidecar container? That's a pretty clever idea. I like the use of a shared volume to access the log file.
upvoted 0 times
Aleta
5 months ago
Using a sidecar container to tail the log file is a practical solution for this scenario.
upvoted 0 times
...
Phuong
5 months ago
Another option could be to use a logging agent like Fluentd to collect and send the log entries.
upvoted 0 times
...
Tamie
6 months ago
Yes, that's a good approach to send the log entries to Stackdriver Logging.
upvoted 0 times
...
...
Keith
6 months ago
Installing Kubernetes on GCE and customizing the Stackdriver Logging configuration? That's overkill for this use case. We don't need to go that route.
upvoted 0 times
Hailey
5 months ago
Yes, that way the sidecar container can read the log file and forward the log entries to Stackdriver Logging without modifying the application.
upvoted 0 times
...
Maryann
5 months ago
That's a great idea! We can deploy the sidecar container alongside the application container in the same pod.
upvoted 0 times
...
Kimbery
5 months ago
You can use a sidecar container to collect the log entries from /var/log/app_messages.log and send them to Stackdriver Logging.
upvoted 0 times
...
...
Dell
7 months ago
Ah, using Fluentd to tail the log file and send it to Stackdriver Logging sounds like the way to go. It's a bit more involved, but it should get the job done.
upvoted 0 times
Shawnee
6 months ago
Yan: Once Fluentd is set up, you can view the log entries from the third-party application in Stackdriver Logging.
upvoted 0 times
...
Yan
6 months ago
User 2: That's right. Make sure to deploy Fluentd as a DaemonSet in your GKE cluster to collect the logs.
upvoted 0 times
...
Hyman
6 months ago
User 1: Yes, you can create a Fluentd configuration file to tail the log file and send it to Stackdriver Logging.
upvoted 0 times
...
...
Noel
7 months 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
6 months ago
D) Write 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.
upvoted 0 times
...
Tanesha
6 months ago
B) Deploy 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.
upvoted 0 times
...
...
Stefania
7 months 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
7 months 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
7 months 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
...

Save Cancel