Between C and D, I think D Reason : When an instance is created, we can specify which service account the instance uses when calling Google Cloud APIs. The instance is automatically configured with access scope and one such access scope is monitoring.write (Link : https://cloud.google.com/compute/docs/access/service- read is to publish metric data and logging.write is to write compute engine logs. Considering above, I believe D as the answer (check whether the agent is running)

Why nnot Answer A as a starting point?

Answer is D.

Ans: D Exam pased and taken on 19/12/2022, 50/50 from this dump without buying the full access.

Answer is D. https://cloud.google.com/logging/docs/agent/logging/troubleshooting. D. Check if fluentd is running is the right answer. C is incorrect as monitoring.write scope is for monitoring agent and not logging agent. The legacy scope for logging is https://www.googleapis.com/auth/logging.write

D is the answer. https://cloud.google.com/logging/docs/agent/logging/troubleshooting#checklist If you are having trouble installing or using the Logging agent, here are some things to check: - Verify that the agent service is running on your VM instance

Ans: D

Ans: D

Submitted D

answer is D

The VM has cloud-platform scope on the VM means Full access if you using the default compute account. I would say answer D is right check is the fluentd daemon running.

https://cloud.google.com/logging/docs/agent/logging/troubleshooting#test-agent

Ans: D

C is not good, “monitoring.write" is use for metric not log

https://cloud.google.com/compute/docs/access/service-accounts#associating_a_service_account_to_an_instance When you create an instance using the gcloud command-line tool or the Google Cloud Console, you can specify which service account the instance uses when calling Google Cloud APIs. The instance is automatically configured with the following access scopes: * https://www.googleapis.com/auth/monitoring.write * ... So D is better than C.

4- Then you should check that the agent is sending data to the correct project. See the following section, Verifying Compute Engine credentials. The link for Verifying Compute Engine credentials is https://cloud.google.com/logging/docs/agent/logging/troubleshooting#verify-creds In this link : a- Verifying access scopes b- Verifying default service account permission ==> Similar to Answer C) but C) Answer talks about monitoring.write instead of logging.write. And in the question they say "The VM has the cloud-platform scope" ==> logging.write is already here. 5- Verifying the agent installation using agent's test log entry in the Logs Explorer ==> Answer A) 6- Testing the agent using ps ax | grep fluentd ==> Answer D) So for me the good answer is A).

If we follow this link : https://cloud.google.com/logging/docs/agent/logging/troubleshooting The action (for Linux VM) are in order : 1- If Linux installation commands result in errors, then make sure that you prefix the installation commands with sudo. 2- Verify that the agent service is running on your VM instance : sudo service google-fluentd status 3- See if the agent has written error messages to the logs.