Topic 1 Question 89
Your architecture calls for the centralized collection of all admin activity and VM system logs within your project. How should you collect these logs from both VMs and services?
All admin and VM system logs are automatically collected by Stackdriver.
Stackdriver automatically collects admin activity logs for most services. The Stackdriver Logging agent must be installed on each instance to collect system logs.
Launch a custom syslogd compute instance and configure your GCP project and VMs to forward all logs to it.
Install the Stackdriver Logging agent on a single compute instance and let it collect all audit and access logs for your environment.
ユーザの投票
コメント(17)
Does not agree with D. B is the nearest answer I feel !
👍 40MeasService2019/10/17Admin and event logs are configured by default. VM System logs require a logging agent to be configured. So A is not valid. Answer is B
👍 19shandy2019/11/26Stackdriver does not require the Stackdriver Logging agent to be installed in order to collect system logs. Stackdriver is a cloud monitoring and logging platform that is integrated with Google Cloud Platform (GCP) and is designed to collect, monitor, and troubleshoot logs from your GCP resources. By default, Stackdriver automatically collects admin activity logs for most GCP services, as well as VM system logs. This means that you don't need to install the Stackdriver Logging agent or any other agents in order to collect these logs - they are automatically collected and centralized by Stackdriver.
However, if you want to collect logs from other sources that are not automatically collected by Stackdriver (e.g. logs from applications running on your VMs, logs from on-premises systems, etc.), you can use the Stackdriver Logging agent to forward these logs to Stackdriver. The agent is a lightweight daemon that runs on your VMs or other hosts, and it can be used to collect logs from various sources and forward them to Stackdriver for centralized storage and analysis.
👍 5omermahgoub2022/12/22
シャッフルモード