Google Professional Cloud DevOps Engineer Question 125
Select 2Google Cloud PlatformYour organization requires that all application logs be retained for 3 years to meet compliance requirements. Currently, logs are ingested into Google Cloud Logging, but they are only retained for the default duration. How can you achieve this long-term retention requirement while optimizing storage costs?
- A
Configure a custom retention policy in Google Cloud Logging to retain the logs for 3 years.
- B
Export the logs to a Cloud Storage bucket with a lifecycle management policy to transition logs to Nearline or Coldline storage after a certain period.
- C
Export the logs to BigQuery and configure a scheduled query to archive logs older than 3 years.
- D
Export the logs to Cloud Pub/Sub and use a subscriber to store them in a Cloud SQL database.
- E
Enable Log Analytics in Google Cloud Logging and set a custom retention period of 3 years.
Show answer and explanation
Correct answers: A, B
Explanation
To meet the 3-year retention requirement, you can either configure a custom retention policy in Google Cloud Logging or export the logs to a cost-effective storage solution like Cloud Storage with lifecycle management. Both approaches ensure compliance while optimizing costs. BigQuery and Cloud SQL are not suitable for this use case, and Log Analytics does not address custom retention needs.
- A. Correct.
Configuring a custom retention policy in Google Cloud Logging allows you to retain logs for a specific duration (up to 3650 days), meeting the 3-year compliance requirement. This is a valid solution.
- B. Correct.
Exporting logs to a Cloud Storage bucket and applying a lifecycle management policy is a cost-effective way to retain logs for long-term storage while optimizing costs. Nearline or Coldline storage is well-suited for infrequently accessed data.
- C. Incorrect.
Exporting logs to BigQuery is not an efficient solution for long-term retention since it is primarily used for analytics and querying. Additionally, archiving logs older than 3 years would require additional management and may not optimize storage costs.
- D. Incorrect.
Exporting logs to Cloud Pub/Sub and storing them in a Cloud SQL database is not practical for log retention. Cloud SQL is not designed for long-term storage of large-scale logging data and would incur higher costs.
- E. Incorrect.
Log Analytics in Google Cloud Logging is used for advanced querying and visualization of logs but does not support setting custom retention periods beyond the Logging default retention. This option does not meet the requirement.