Explanation:
The correct approach involves creating the logging bucket in Logging and setting up the sink for organization logs via the CLI. Other options fall short because: creating a logging bucket in the console is done under Logs Storage in Logging, not Cloud Storage; some methods cannot be executed in the Console; and certain options do not fulfill the requirement of aggregating logs in one location. For further details, refer to the guide on aggregating and storing your organization's logs.
Ultimate access to all questions.
No comments yet.
Imagine you're tasked with designing a new logs collection system for your organization, with the requirement to aggregate all audit logs from every project into a single location. How would you achieve this?
A
Establish a logs sink via the CLI, detailing the logs to collect, the logging bucket, the organization, and include the –include-children flag.
B
Set up a dedicated Project for log collection, and within it, create a logging bucket in Cloud Storage through the console.
C
Initiate a dedicated Project for log collection, and within it, create a logging bucket in Logging via the console.
D
Implement a logs sink in each Project directing to the logging bucket.
E
Create a logs sink in the console, selecting the logs to collect, the logging bucket, the organization, and all projects within the organization.