Your company has an application that is running on multiple instances of Compute Engine. It generates 1 TB per day of logs. For compliance reasons, the logs need to be kept for at least two years. The logs need to be available for active query for 30 days. After that, they just need to be retained for audit purposes. You want to implement a storage solution that is compliant, minimizes costs, and follows Google-recommended practices. What should you do?

This solution leverages Cloud Logging agents to collect logs efficiently and centrally. Exporting logs to a regional Cloud Storage bucket provides a cost-effective, scalable, and compliant storage solution. The Object Lifecycle rule automatically transitions logs to Coldline Storage after 30 days, reducing costs while maintaining availability for audit. Finally, a bucket-level retention policy with bucket lock ensures compliance with the two-year retention requirement, preventing accidental or malicious deletion. The incorrect options either fail to meet compliance requirements, are less cost-effective, or involve unnecessary manual processes. Using a cron job for log upload is less reliable and scalable than Cloud Logging agents. While BigQuery can store logs, it's generally more expensive for long-term, infrequently accessed archival than Cloud Storage.