Google Professional Cloud Security Engineer Question 350
Select 3Google Cloud PlatformYou are managing a Cloud Storage bucket that stores sensitive customer data. To optimize storage costs while ensuring compliance with data retention requirements, you need to implement an object lifecycle policy. The policy must ensure that files older than 30 days are moved to Nearline Storage and files older than 365 days are deleted. Which steps should you take to configure this lifecycle policy?
- A
Define a lifecycle rule with a condition to move objects to Nearline Storage after 30 days.
- B
Define a lifecycle rule with a condition to delete objects older than 365 days.
- C
Set the default storage class of the bucket to Nearline Storage.
- D
Apply the lifecycle policy to the bucket where the sensitive data is stored.
- E
Enable Object Versioning to track changes to the objects before applying the lifecycle policy.
Show answer and explanation
Correct answers: A, B, D
Explanation
To meet the requirements of moving files older than 30 days to Nearline Storage and deleting files older than 365 days, you need to define lifecycle rules for both conditions and apply the policy to the relevant bucket. Setting the default storage class or enabling Object Versioning is not necessary for this specific use case.
- A. Correct.
This is correct. A lifecycle rule must define a condition to move objects to Nearline Storage after 30 days to optimize costs while retaining access to the data.
- B. Correct.
This is correct. A lifecycle rule must define a condition to delete objects after 365 days to ensure data is removed in alignment with the retention requirements.
- C. Incorrect.
This is incorrect. Setting the default storage class to Nearline Storage impacts all objects uploaded to the bucket but does not align with the specific lifecycle requirements for transitioning and deleting objects.
- D. Correct.
This is correct. The lifecycle policy must be applied to the bucket where the sensitive data is stored to ensure it takes effect.
- E. Incorrect.
This is incorrect. While enabling Object Versioning is useful for tracking changes to objects, it is not a requirement for configuring lifecycle policies.