Exam Associate Cloud Engineer topic 1 question 55 discussion

The question mentioned that "GKE container emitted a huge number of logs", in my opinion A is correct.

I think A is right. https://cloud.google.com/logging/docs/api/v2/resource-list GKE Containers have more log than GKE Cluster Operations: .-GKE Containe: cluster_name: An immutable name for the cluster the container is running in. namespace_id: Immutable ID of the cluster namespace the container is running in. instance_id: Immutable ID of the GCE instance the container is running in. pod_id: Immutable ID of the pod the container is running in. container_name: Immutable name of the container. zone: The GCE zone in which the instance is running. VS .-GKE Cluster Operations project_id: The identifier of the GCP project associated with this resource, such as "my-project". cluster_name: The name of the GKE Cluster. location: The location in which the GKE Cluster is running.

Your projects incurred more costs than you expected last month. Your research reveals that a development GKE container emitted a huge number of logs, which resulted in higher costs. You want to disable the logs quickly using the minimum number of steps. What should you do? A. 1. Go to the Logs ingestion window in Stackdriver Logging, and disable the log source for the GKE container resource. B. 1. Go to the Logs ingestion window in Stackdriver Logging, and disable the log source for the GKE Cluster Operations resource. C. 1. Go to the GKE console, and delete existing clusters. 2. Recreate a new cluster. 3. Clear the option to enable legacy Stackdriver Logging. D. 1. Go to the GKE console, and delete existing clusters. 2. Recreate a new cluster. 3. Clear the option to enable legacy Stackdriver Monitoring.

A seems more correct as it also uses the fewes steps also

Just as a side note. Stackdriver is now Google Cloud Operations Suite.

The correct answer is A. To disable the logs quickly using the minimum number of steps, you should go to the Logs ingestion window in Stackdriver Logging and disable the log source for the GKE container resource. This will prevent the GKE container from emitting logs, which will in turn reduce the amount of log data generated and lower the costs incurred. Answer B is incorrect because disabling the log source for the GKE Cluster Operations resource would not stop the logs emitted by the GKE container, and would not reduce the amount of log data generated. Answers C and D are incorrect because deleting and recreating the GKE cluster is not a recommended approach for disabling logs. Additionally, clearing the option to enable legacy Stackdriver Logging or Monitoring would not disable the logs emitted by the GKE container.

A is correct

A can do it with fewest steps

Currently B is correct. (Stackdriver Logging has been named Cloud Logging.) https://cloud.google.com/stackdriver/docs/solutions/gke/installing#migrating

Go for A

C,D are straight forward you can eliminate and decide between A & B .. A makes more sense .. logical thinking required to solve it quickly.

Go for A

A is correct. Target GKE containers since that is what is emitting the most logs

Go to the Logs ingestion window in Stackdriver Logging, and disable the log source for the GKE container resource.

A is right answer

A is ans

A. 1. Go to the Logs ingestion window in Stackdriver Logging, and disable the log source for the GKE container resource.