Explanation:
To centralize logs in the security project while excluding Apache logs, you should first create a Logs bucket in the security project. Then, for each project, set up a sink in the Logs router that directs logs to this bucket, using a filter rate of 100 to ensure all Apache logs are excluded. Options B and E are incorrect as they suggest keeping logs within individual projects, which doesn't meet the centralization requirement. Option C is incorrect because a filter rate of 0 would not exclude any Apache logs. For more details, refer to Google Cloud's documentation on log exclusions.
Ultimate access to all questions.
No comments yet.
Your organization manages multiple Google Cloud projects, each representing different environments like development, test, pre-production, and production. There's a need to implement a centralized logging system where logs from all environments are sent to a dedicated security project, with the exception of logs generated by an Apache application. Which two actions would you take to meet this requirement?
A
Establish a Logs bucket within the security project.
B
Set up a Logs bucket in every individual project.
C
For each project, configure a sink in the Logs router that directs logs to the security project's Logs bucket, applying a filter with a rate of 0 to exclude Apache logs.
D
For each project, configure a sink in the Logs router that directs logs to the security project's Logs bucket, applying a filter with a rate of 100 to exclude Apache logs.
E
For each project, configure a sink in the Logs router that directs logs to its own Logs bucket, applying a filter with a rate of 100 to exclude Apache logs.