You are creating a Kubernetes Engine cluster to deploy multiple pods inside the cluster. All container logs must be stored in BigQuery for later analysis. You want to follow Google- recommended…

Question

Options

• ATurn on Stackdriver Logging during the Kubernetes Engine cluster creation.
• BTurn on Stackdriver Monitoring during the Kubernetes Engine cluster creation.
• CDevelop a custom add-on that uses Cloud Logging API and BigQuery API. Deploy the add-on to
• DUse the Stackdriver Logging export feature to create a sink to Cloud Storage. Create a Cloud
• EUse the Stackdriver Logging export feature to create a sink to BigQuery. Specify a filter

• A
  63% (27)
• B
  12% (5)
• C
  19% (8)
• D
  7% (3)

Explanation

A Is correct because creating a cluster with Stackdriver Logging option will enable all the container logs to be stored in Stackdriver Logging. B Is not correct because creating a cluster with Stackdriver Monitoring option will enable monitoring metrics to be gathered, but it has nothing to do with logging. C is not correct, because even if you can develop a Kubernetes addon that will send logs to BigQuery, this is not a Google-recommended practice. D is incorrect because this is not a Google recommended practice. E Is correct because Stackdriver Logging support exporting logs to BigQuery by creating sinks (see links below). https://cloud.google.com/kubernetes-engine/docs/how-to/logging https://cloud.google.com/logging/docs/export/configure_export_v2 https://kubernetes.io/docs/reference/labels-annotations-taints/

No community discussion yet for this question.