You want to allow your operations team to store logs from all the production projects in your Organization, without including logs from other projects. All of the production projects are contained in a folder. You want to ensure that all logs for existing and new production projects are captured automatically. What should you do?

Creating an aggregated export on the Production folder ensures that logs from all current and future projects within that folder are automatically captured. This centralizes log collection for the operations team. Setting the log sink to a Cloud Storage bucket in an operations project provides a cost-effective and scalable storage solution, accessible to the operations team. Creating an aggregated export on the Organization resource would capture logs from all projects, including non-production ones, which is not desired. Creating individual log exports in each production project is not scalable or automatic for new projects. Storing logs in BigQuery datasets within each production project and granting IAM access would be overly complex for simple log storage and analysis, and doesn't centralize the logs effectively for the operations team.