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

Noah

1 months ago

Stackdriver Logging, huh? Sounds like a service that's about as reliable as a stack of drunk toddlers.

upvoted 0 times

...

Simona

1 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

10 days ago

Using a sidecar container to tail the log file is a practical solution for this scenario.

upvoted 0 times

...

Phuong

16 days ago

Another option could be to use a logging agent like Fluentd to collect and send the log entries.

upvoted 0 times

...

Tamie

23 days ago

Yes, that's a good approach to send the log entries to Stackdriver Logging.

upvoted 0 times

...

Keith

2 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 days 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

12 days ago

That's a great idea! We can deploy the sidecar container alongside the application container in the same pod.

upvoted 0 times

...

Kimbery

16 days 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

2 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

27 days 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

28 days 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

1 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

2 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

1 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

2 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

2 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

2 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

3 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

...