SCS-C02 Question 386
Single answerYour company is using Amazon S3 to store confidential business data. To optimize costs and comply with data retention policies, you need to create a lifecycle policy that transitions objects to Amazon S3 Glacier after 60 days and permanently deletes objects older than 365 days. Which configuration step is required to ensure this lifecycle policy works as intended?
- A
Ensure the bucket versioning is enabled before applying the lifecycle policy.
- B
Define a lifecycle rule with a transition action to move objects to S3 Glacier after 60 days and an expiration action after 365 days.
- C
Enable server-side encryption (SSE) with AWS KMS for the bucket before creating the lifecycle policy.
- D
Set bucket-level access policies to allow lifecycle transitions to S3 Glacier.
Show answer and explanation
Correct answer: B
Explanation
To implement a lifecycle policy for transitioning objects to S3 Glacier and expiring objects after a specified period, you must define a lifecycle rule with the necessary transition and expiration actions. This configuration ensures that objects are moved to lower-cost storage after 60 days and deleted after 365 days, optimizing cost and complying with retention policies. Other options, such as enabling versioning or encryption, are not required for the lifecycle policy to function as described.
- A. Incorrect.
Bucket versioning is not required to apply lifecycle policies. While versioning can interact with lifecycle rules for managing object versions, it is not mandatory for basic lifecycle rule functionality.
- B. Correct.
This is the correct option. Lifecycle rules can be configured to transition objects to S3 Glacier after a specified number of days and delete objects after a specific period. This configuration meets the scenario requirements.
- C. Incorrect.
Enabling server-side encryption (SSE) is unrelated to lifecycle policies. Lifecycle policies manage object transitions and expirations but do not require encryption to function.
- D. Incorrect.
Lifecycle policies operate independently of bucket-level access policies. While access policies control permissions, they do not affect the functionality of lifecycle rules.