The answer is A. The practice for managing logs generated on Compute Engine on Google Cloud is to install the Cloud Logging agent and send them to Cloud Logging. The sent logs will be aggregated into a Cloud Logging sink and exported to Cloud Storage. The reason for using Cloud Storage as the destination for the logs is that the requirement in question requires setting up a lifecycle based on the storage period. In this case, the log will be used for active queries for 30 days after it is saved, but after that, it needs to be stored for a longer period of time for auditing purposes. If the data is to be used for active queries, we can use BigQuery's Cloud Storage data query feature and move the data past 30 days to Coldline to build a cost-optimal solution. Therefore, the correct answer is as follows 1. Install the Cloud Logging agent on all instances. Create a sync that exports the logs to the region's Cloud Storage bucket. 3. Create an Object Lifecycle rule to move the files to the Coldline Cloud Storage bucket after one month. 4. 4. set up a bucket-level retention policy using bucket locking."

No need to look at any other options.

None of the options are correct: A - It should be archive (>= 365 days) and not coldline ( >= 90 days) - Proposed solution is more expensive that what is possible. Also no way to query unless you use BigQuery external tables. B & C - Wrong because CRON is not the way to do this. D - Wrong because data is deleted after 30 days and not retained for 2 years.

Answer A is misleading/confusing: "3. Create an Object Lifecycle rule to move files into a Coldline Cloud Storage bucket after one month." A lifecycle rule will NOT move files in another bucket (coldline bucket etc). It will just change the storage class of the file.

A is correct

A is correct.

A. 1. Install a Cloud Logging agent on all instances. 2. Create a sink to export logs into a regional Cloud Storage bucket. 3. Create an Object Lifecycle rule to move files into a Coldline Cloud Storage bucket after one month. 4. Configure a retention policy at the bucket level using bucket lock. This approach would allow you to use Cloud Logging to collect and export the logs from the Compute Engine instances into a Cloud Storage bucket. You can then use an Object Lifecycle rule to automatically move the logs from the regional bucket to a Coldline bucket after one month, which will reduce storage costs for logs that are not actively being queried. By configuring a retention policy using bucket lock, you can ensure that the logs are retained for at least two years for audit purposes. This approach follows Google-recommended practices for storing logs and minimizing costs.

A Is the Correct Answer

A is perfect answer… the rest doesn’t sound rational

A is ok

A is the correct answer

I agree with A, There is no need of BigQuery.

A is fine

For compliance reasons, the logs need to be kept for at least two years... In Bigquery time partitioned after 30 days ..how the logs be present for 2 years ..Hence going with A

A is a no-brainer

A is ok

when a partition expires, the data in the partition is no longer available