Google Professional Cloud DevOps Engineer
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
You have a set of applications running on a Google Kubernetes Engine (GKE) cluster with Stackdriver Kubernetes Engine Monitoring enabled. A new third-party containerized application, which cannot be modified or reconfigured, writes logs to /var/log/app_messages.log. How can you ensure these logs are ingested into Stackdriver Logging?_
A
Use the default Stackdriver Kubernetes Engine Monitoring agent configuration.
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 Stackdriver Logging.
C
Install 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.
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.