S3 Lifecycle Policy practice questions

A company keeps daily database backups in an S3 bucket. They may restore from backups during the first 30 days if there is an issue. After 30 days, backups are rarely restored, but must be retained for 2 years. Which lifecycle strategy most cost-effectively meets these requirements?

Trap 1: Delete backups after 30 days to avoid storage costs, since restores…

Deleting after 30 days violates the stated requirement to retain backups for 2 years.

Trap 2: Keep all backups in S3 Standard for the entire 2-year retention…

S3 Standard is usually more expensive than tiered archival classes for long-term, infrequent access.

Trap 3: Move backups to S3 Glacier Deep Archive immediately after creation,…

Immediate Deep Archive storage may make restorations during the first 30 days too slow.

A
Delete backups after 30 days to avoid storage costs, since restores are rare.
Why wrong: Deleting after 30 days violates the stated requirement to retain backups for 2 years.
B
Keep all backups in S3 Standard for the entire 2-year retention period.
Why wrong: S3 Standard is usually more expensive than tiered archival classes for long-term, infrequent access.
C
Use an S3 lifecycle policy to keep backups in S3 Standard for 30 days, then transition them to S3 Glacier Deep Archive for the remainder of the 2-year retention period.
A lifecycle transition after the initial restore window reduces cost while still meeting the 2-year retention requirement.
D
Move backups to S3 Glacier Deep Archive immediately after creation, even for the first 30 days.
Why wrong: Immediate Deep Archive storage may make restorations during the first 30 days too slow.

Question 2mediummultiple choice

A SaaS company uses an S3 bucket for database backups created daily. Backups are rarely restored; the company’s documented RTO is 24 hours, and the compliance policy requires backups be kept for 90 days. The team currently stores all backups in S3 Standard, which is costly.

Which single lifecycle policy change is most cost-optimized while still meeting the 24-hour RTO and 90-day retention?

Trap 1: Add a lifecycle rule to transition backups older than 1 day to S3…

While S3 Glacier Instant Retrieval offers immediate access, meeting the RTO, it is generally a more expensive storage class for data that is infrequently accessed, especially compared to Glacier Flexible Retrieval. For backups that are older than one day and expected to be rarely retrieved, the higher per-GB retrieval cost and storage cost of Instant Retrieval make it less cost-effective. This choice fails to optimize costs effectively when a cheaper alternative with an acceptable RTO exists.

Trap 2: Add a lifecycle rule to transition backups older than 1 day to S3…

S3 Glacier Deep Archive is designed for the lowest-cost archival storage, but its standard retrieval times typically range from 12 to 48 hours, with bulk retrievals taking up to 48 hours. This extended retrieval period directly conflicts with a strict 24-hour Recovery Time Objective (RTO), as there's no guarantee of data availability within the required timeframe. Therefore, despite meeting the 90-day retention, this storage class is unsuitable due to its potentially slow retrieval performance.

Trap 3: Add a lifecycle rule to transition backups older than 1 day to S3…

This option is fundamentally flawed because it specifies deleting backups after only 7 days, which directly violates the required 90-day data retention policy. While S3 One Zone-IA offers cost savings by storing data in a single Availability Zone, its primary drawback here is the insufficient retention period. The solution must ensure data is available for the full 90 days, making this lifecycle rule unacceptable.

A
Add a lifecycle rule to transition backups older than 1 day to S3 Glacier Flexible Retrieval, and keep them until day 90.
This option correctly leverages S3 Lifecycle rules to transition older, less frequently accessed backups to S3 Glacier Flexible Retrieval. This storage class provides significant cost savings compared to S3 Standard or S3-IA, while still supporting retrieval times measured in hours, which comfortably meets a 24-hour Recovery Time Objective (RTO). Maintaining retention until day 90 also satisfies the long-term data retention requirement efficiently.
B
Add a lifecycle rule to transition backups older than 1 day to S3 Glacier Instant Retrieval, and keep them until day 90.
Why wrong: While S3 Glacier Instant Retrieval offers immediate access, meeting the RTO, it is generally a more expensive storage class for data that is infrequently accessed, especially compared to Glacier Flexible Retrieval. For backups that are older than one day and expected to be rarely retrieved, the higher per-GB retrieval cost and storage cost of Instant Retrieval make it less cost-effective. This choice fails to optimize costs effectively when a cheaper alternative with an acceptable RTO exists.
C
Add a lifecycle rule to transition backups older than 1 day to S3 Glacier Deep Archive, and keep them until day 90 with no restore configuration.
Why wrong: S3 Glacier Deep Archive is designed for the lowest-cost archival storage, but its standard retrieval times typically range from 12 to 48 hours, with bulk retrievals taking up to 48 hours. This extended retrieval period directly conflicts with a strict 24-hour Recovery Time Objective (RTO), as there's no guarantee of data availability within the required timeframe. Therefore, despite meeting the 90-day retention, this storage class is unsuitable due to its potentially slow retrieval performance.
D
Add a lifecycle rule to transition backups older than 1 day to S3 One Zone-IA, and delete them after 7 days.
Why wrong: This option is fundamentally flawed because it specifies deleting backups after only 7 days, which directly violates the required 90-day data retention policy. While S3 One Zone-IA offers cost savings by storing data in a single Availability Zone, its primary drawback here is the insufficient retention period. The solution must ensure data is available for the full 90 days, making this lifecycle rule unacceptable.

Question 3easymultiple choice

A company stores user uploads in an S3 bucket. Objects are accessed rarely after upload, but when an object is accessed, it must be retrievable quickly (minutes to a few hours). Objects must be retained for at least 18 months. The team wants to reduce storage cost while meeting these requirements. Which lifecycle configuration best fits these requirements?

Trap 1: Keep all objects in S3 Standard permanently to avoid lifecycle…

Keeping objects in S3 Standard does not reduce storage cost. Lifecycle transitions are specifically designed to move infrequently accessed data to lower-cost storage classes after a delay. Even if there are per-transition request costs, the ongoing savings from using a cheaper storage class for the long retention period typically outweigh those transition request costs.

Trap 2: After 30 days, transition objects to S3 Intelligent-Tiering, and…

Intelligent-Tiering can reduce cost when access patterns are unpredictable, but the expiration setting must still meet the business retention requirement. Expiring at 12 months violates the requirement to retain objects for at least 18 months, so this option would fail compliance.

Trap 3: After 30 days, transition objects to S3 Glacier Deep Archive, and…

Deep Archive is generally the lowest-cost option for data that is extremely rarely accessed, but it has much slower restore times compared with Instant Retrieval. Because the prompt states that when accessed, objects must be retrievable quickly (minutes to a few hours), Deep Archive is not the best fit even though it would satisfy the 18-month retention requirement and would reduce cost.

A
Keep all objects in S3 Standard permanently to avoid lifecycle transition fees.
Why wrong: Keeping objects in S3 Standard does not reduce storage cost. Lifecycle transitions are specifically designed to move infrequently accessed data to lower-cost storage classes after a delay. Even if there are per-transition request costs, the ongoing savings from using a cheaper storage class for the long retention period typically outweigh those transition request costs.
B
After 30 days, transition objects to S3 Glacier Instant Retrieval, and after 18 months, expire (delete) the objects.
The prompt requires (1) cost reduction for data that becomes infrequently accessed and (2) quick retrieval when accessed again, and (3) a minimum retention of at least 18 months. Glacier Instant Retrieval is intended for data that is accessed occasionally and needs fast retrieval. Transitioning after 30 days moves the long-term, rarely accessed portion of the data to a cheaper class, while expiring at 18 months satisfies the explicit retention requirement (the objects remain for at least 18 months).
C
After 30 days, transition objects to S3 Intelligent-Tiering, and set expiration to 12 months.
Why wrong: Intelligent-Tiering can reduce cost when access patterns are unpredictable, but the expiration setting must still meet the business retention requirement. Expiring at 12 months violates the requirement to retain objects for at least 18 months, so this option would fail compliance.
D
After 30 days, transition objects to S3 Glacier Deep Archive, and set expiration to 18 months.
Why wrong: Deep Archive is generally the lowest-cost option for data that is extremely rarely accessed, but it has much slower restore times compared with Instant Retrieval. Because the prompt states that when accessed, objects must be retrievable quickly (minutes to a few hours), Deep Archive is not the best fit even though it would satisfy the 18-month retention requirement and would reduce cost.

Question 4mediummultiple choice

A marketing site stores logs in S3. Logs are queried for 30 days, rarely accessed for one year, and then retained for compliance. What should reduce storage cost? The design must avoid adding custom operational scripts.

Trap 1: Keep all logs in S3 Standard indefinitely

S3 Standard is more expensive for rarely accessed archival data.

Trap 2: Use EBS snapshots for the logs

EBS snapshots are not the right storage model for application log objects.

Trap 3: Move all logs immediately to S3 Glacier Deep Archive

Immediate deep archive can make recent query access slow and expensive.

A
S3 lifecycle policy that transitions objects to lower-cost storage classes over time
Lifecycle rules automate transitions based on age, matching storage cost to access patterns.
B
Keep all logs in S3 Standard indefinitely
Why wrong: S3 Standard is more expensive for rarely accessed archival data.
C
Use EBS snapshots for the logs
Why wrong: EBS snapshots are not the right storage model for application log objects.
D
Move all logs immediately to S3 Glacier Deep Archive
Why wrong: Immediate deep archive can make recent query access slow and expensive.

Question 5mediummultiple choice

A company stores application logs in an S3 bucket. They retain logs for 180 days. Compliance requires that the logs be immutable once written, but the business only reviews logs about once per month. Currently, the team stores everything in S3 Standard, and their monthly S3 bill is too high. They want to reduce storage cost without changing the requirement to keep logs for 180 days.

Which lifecycle approach best meets the goal?

Trap 1: Use a lifecycle policy to transition objects older than 30 days to…

Deep Archive is cheaper, but deletion after 30 days violates the 180-day retention requirement.

Trap 2: Use a lifecycle policy to transition objects older than 30 days to…

Intelligent-Tiering can help, but removing a minimum duration is not necessary and adds complexity versus a clear monthly-access pattern.

Trap 3: Disable lifecycle management and instead lower costs by deleting…

Deleting immediately reduces cost but directly breaks the required 180-day retention and immutability needs.

A
Use a lifecycle policy to transition objects older than 30 days to S3 Standard-IA, and keep them there until day 180.
Logs accessed about monthly match Standard-IA economics and still provide fast retrieval.
B
Use a lifecycle policy to transition objects older than 30 days to S3 Glacier Deep Archive and delete after 30 days.
Why wrong: Deep Archive is cheaper, but deletion after 30 days violates the 180-day retention requirement.
C
Use a lifecycle policy to transition objects older than 30 days to S3 Intelligent-Tiering with no minimum storage duration.
Why wrong: Intelligent-Tiering can help, but removing a minimum duration is not necessary and adds complexity versus a clear monthly-access pattern.
D
Disable lifecycle management and instead lower costs by deleting objects immediately after they are written.
Why wrong: Deleting immediately reduces cost but directly breaks the required 180-day retention and immutability needs.

Question 6mediummultiple choice

Which single lifecycle policy change is most cost-optimized while still meeting the 24-hour RTO and 90-day retention?

Trap 1: Add a lifecycle rule to transition backups older than 1 day to S3…

Instant Retrieval can meet the RTO but usually costs more than Flexible Retrieval for infrequent backups.

Trap 2: Add a lifecycle rule to transition backups older than 1 day to S3…

Deep Archive restore times are typically longer and may conflict with a strict 24-hour RTO expectation.

Trap 3: Add a lifecycle rule to transition backups older than 1 day to S3…

One Zone-IA reduces cost but deletion after 7 days breaks the required 90-day retention.

A
Add a lifecycle rule to transition backups older than 1 day to S3 Glacier Flexible Retrieval, and keep them until day 90.
Glacier Flexible Retrieval is intended for backups with infrequent access and supports restores within an RTO measured in hours.
B
Add a lifecycle rule to transition backups older than 1 day to S3 Glacier Instant Retrieval, and keep them until day 90.
Why wrong: Instant Retrieval can meet the RTO but usually costs more than Flexible Retrieval for infrequent backups.
C
Add a lifecycle rule to transition backups older than 1 day to S3 Glacier Deep Archive, and keep them until day 90 with no restore configuration.
Why wrong: Deep Archive restore times are typically longer and may conflict with a strict 24-hour RTO expectation.
D
Add a lifecycle rule to transition backups older than 1 day to S3 One Zone-IA, and delete them after 7 days.
Why wrong: One Zone-IA reduces cost but deletion after 7 days breaks the required 90-day retention.

Question 7hardmultiple choice

Based on the exhibit, the company stores application logs in Amazon S3 for 400 days. The logs are read heavily for the first 30 days, occasionally for the next 90 days, and very rarely after that. Retrieval after day 120 can take up to several hours, but the data must remain available until day 400. Which lifecycle policy is the most cost-effective fit?

Exhibit

Current bucket: app-logs-prod
Objects: compressed JSON logs, 150 GB per month
Access pattern:
  Days 0-30: frequent reads for troubleshooting
  Days 31-120: occasional reads
  Days 121-400: rare reads, retrieval can take hours
Compliance: retain all logs for 400 days, then delete
Current storage class: S3 Standard for all objects
Monthly S3 bill trend: rising steadily as log volume grows

Trap 1: Keep all logs in S3 Standard for 400 days and enable requester pays…

Requester Pays only shifts request costs to whoever accesses the object. It does not reduce the storage cost of retaining the logs for 400 days, and it is not appropriate when the company itself must retain and read the data for compliance and troubleshooting.

Trap 2: Transition logs directly from S3 Standard to S3 Glacier Deep…

Deep Archive is cheaper for very cold data, but retrieval is significantly slower than the several-hour recovery window described in the exhibit. That makes it a poor fit for the period after day 120 when the logs must still be retrievable within hours.

Trap 3: Move logs to S3 Intelligent-Tiering only and disable lifecycle…

Intelligent-Tiering is most useful when access patterns are unknown or change frequently. In this scenario, the access pattern is clearly defined, so explicit lifecycle transitions are usually cheaper than paying the monitoring overhead of Intelligent-Tiering across the entire retention period.

A
Keep all logs in S3 Standard for 400 days and enable requester pays to reduce the company's bill.
Why wrong: Requester Pays only shifts request costs to whoever accesses the object. It does not reduce the storage cost of retaining the logs for 400 days, and it is not appropriate when the company itself must retain and read the data for compliance and troubleshooting.
B
Transition logs to S3 Standard-IA after 30 days, then to S3 Glacier Flexible Retrieval after 120 days, and expire them at 400 days.
This follows the access pattern and the retrieval-time requirement. S3 Standard fits the heavy-read period in the first 30 days. Standard-IA is a lower-cost choice for the next 90 days when access is only occasional, and Glacier Flexible Retrieval is appropriate after day 120 because the logs are rarely read and can tolerate retrieval in hours. Expiration at day 400 satisfies the retention requirement exactly.
C
Transition logs directly from S3 Standard to S3 Glacier Deep Archive after 30 days and expire them at 400 days.
Why wrong: Deep Archive is cheaper for very cold data, but retrieval is significantly slower than the several-hour recovery window described in the exhibit. That makes it a poor fit for the period after day 120 when the logs must still be retrievable within hours.
D
Move logs to S3 Intelligent-Tiering only and disable lifecycle transitions because access is unpredictable.
Why wrong: Intelligent-Tiering is most useful when access patterns are unknown or change frequently. In this scenario, the access pattern is clearly defined, so explicit lifecycle transitions are usually cheaper than paying the monitoring overhead of Intelligent-Tiering across the entire retention period.