Your company has a Google Cloud resource hierarchy with folders for production test and development Your cyber security team needs to review your company's Google Cloud security posture to accelerate security issue identification and resolution You need to centralize the logs generated by Google Cloud services from all projects only inside your production folder to allow for alerting and near-real time analysis.
What should you do?
- Enable the Workflows API and route all the logs to Cloud Logging
- Create a central Cloud Monitoring workspace and attach all related projects
- Create an aggregated log sink associated with the production folder that uses a Pub Sub topic as the destination
- Create an aggregated log sink associated with the production folder that uses a Cloud Logging bucket as the destination
Answer(s): D
Explanation:
The best option for centralizing the logs generated by Google Cloud services from all projects only inside your production folder is to create an aggregated log sink associated with the production folder that uses a Cloud Logging bucket as the destination. An aggregated log sink is a log sink that collects logs from multiple sources, such as projects, folders, or organizations. A Cloud Logging bucket is a storage location for logs that can be used as a destination for log sinks. By creating an aggregated log sink with a Cloud Logging bucket, you can collect and store all the logs from the production folder in one place and allow for alerting and near-real time analysis using Cloud Monitoring and Cloud Operations.
Reveal Solution Next Question