SAA-C03 Question 409
Select 2A company is using Amazon S3 to store large volumes of data. Some of the data needs to be retained for regulatory compliance, while other data becomes infrequently accessed after 30 days and should be cost-optimized. The company also wants to ensure automatic deletion of data that is no longer needed after 5 years. How should the company design its S3 lifecycle policy to meet these requirements?
- A
Move infrequently accessed data to S3 Intelligent-Tiering after 30 days.
- B
Move infrequently accessed data to S3 Standard-IA after 30 days.
- C
Delete data that is no longer needed after 5 years.
- D
Enable S3 Glacier Deep Archive for compliance data after 30 days.
- E
Use object versioning to retain all versions of data for compliance purposes.
Show answer and explanation
Correct answers: B, C
Explanation
The correct approach involves transitioning infrequently accessed data to S3 Standard-IA after 30 days to optimize costs and setting a lifecycle policy to delete unneeded data after 5 years. S3 Intelligent-Tiering is not ideal here because access patterns are predictable. Glacier Deep Archive and versioning are not required to meet the specified requirements in this scenario.
- A. Incorrect.
S3 Intelligent-Tiering is generally used for unpredictable access patterns, where you do not know when or how often an object will be accessed. In this scenario, the data is explicitly mentioned as infrequently accessed after 30 days, so a more cost-optimized storage class like S3 Standard-IA is more suitable.
- B. Correct.
S3 Standard-IA is a cost-optimized storage class for data that is accessed less frequently. Moving the data here after 30 days meets the requirement for cost optimization.
- C. Correct.
A lifecycle rule can be configured to delete objects after a specified period, such as 5 years, which satisfies the requirement to automatically delete unneeded data.
- D. Incorrect.
S3 Glacier Deep Archive is designed for long-term archival storage, but the compliance requirement mentioned does not specify transitioning to archival storage. Additionally, the scenario does not state that compliance data becomes infrequently accessed after 30 days.
- E. Incorrect.
Object versioning is useful for retaining multiple versions of objects, but it is not necessary in this scenario, as the compliance requirement can be met without retaining all versions.