S3 Lifecycle Policy practice questions

A studio keeps 4 PB of completed video projects in Amazon S3. Editors work on active projects for about 60 days, auditors occasionally review the same objects for several months, and legal policy requires retention for 7 years. Retrieval of very old files can take hours. Which three actions should the architect recommend? Select three.

Trap 1: Keep the files in S3 Standard indefinitely so retrieval is always…

S3 Standard provides fast access, but it is unnecessarily expensive for multi-year retention of footage that is rarely needed.

Trap 2: Copy the files to a single EBS volume for lower per-GB cost.

EBS is block storage and is not suitable for massive archival libraries with lifecycle and retention requirements like these.

A
Transition objects to S3 Standard-IA after 60 days.
Standard-IA is a good fit after the active editing window because the objects are accessed less often but still need relatively quick retrieval.
B
Transition objects to S3 Glacier Deep Archive after the review period ends.
Deep Archive minimizes long-term storage spend when the oldest footage can tolerate hour-scale retrieval, exactly as stated in the scenario.
C
Expire objects after 7 years.
Lifecycle expiration at the end of the legal retention window stops unnecessary storage charges after the policy requirement is satisfied.
D
Keep the files in S3 Standard indefinitely so retrieval is always fast.
Why wrong: S3 Standard provides fast access, but it is unnecessarily expensive for multi-year retention of footage that is rarely needed.
E
Copy the files to a single EBS volume for lower per-GB cost.
Why wrong: EBS is block storage and is not suitable for massive archival libraries with lifecycle and retention requirements like these.

Question 2mediummultiple 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 3mediummultiple 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 4mediummultiple choice

A test environment 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?

Trap 1: Keep all logs in S3 Standard indefinitely

S3 Standard is more expensive for rarely accessed archival data.

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

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

Trap 3: Use EBS snapshots for the logs

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

A
Keep all logs in S3 Standard indefinitely
Why wrong: S3 Standard is more expensive for rarely accessed archival data.
B
Move all logs immediately to S3 Glacier Deep Archive
Why wrong: Immediate deep archive can make recent query access slow and expensive.
C
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.
D
Use EBS snapshots for the logs
Why wrong: EBS snapshots are not the right storage model for application log objects.

Question 5easymultiple choice

A team stores application logs in Amazon S3. They need access to the logs only occasionally for troubleshooting (infrequent access), and they want to reduce storage cost automatically over time without manually moving objects. What should they implement?

Trap 1: An S3 lifecycle policy that deletes objects after 1 day to…

Deleting after 1 day would remove data before it can be used for occasional troubleshooting. Storage cost optimization must still respect retention and troubleshooting requirements; lifecycle rules should transition to cheaper classes rather than delete immediately unless deletion is explicitly acceptable.

Trap 2: An S3 lifecycle policy that keeps all objects in S3 Standard and…

Staying in S3 Standard does not address the cost driver (storage class pricing based on access frequency). “Compression at read time” is not an S3 lifecycle storage class optimization mechanism and would not directly lower S3 storage class charges as requested.

Trap 3: A policy that changes bucket encryption from SSE-S3 to SSE-KMS to…

Changing encryption type affects security and KMS key usage, not the fundamental S3 storage class pricing model. It is not a reliable method to reduce storage costs for infrequent access workloads.

A
An S3 lifecycle policy that transitions objects to a lower-cost storage class after a set number of days
S3 lifecycle policies can automatically transition objects based on age to storage classes priced for infrequent access (for example, Standard-IA or Glacier-based classes). This preserves the data for later troubleshooting while lowering storage cost as objects become older.
B
An S3 lifecycle policy that deletes objects after 1 day to eliminate storage costs
Why wrong: Deleting after 1 day would remove data before it can be used for occasional troubleshooting. Storage cost optimization must still respect retention and troubleshooting requirements; lifecycle rules should transition to cheaper classes rather than delete immediately unless deletion is explicitly acceptable.
C
An S3 lifecycle policy that keeps all objects in S3 Standard and only applies compression at read time
Why wrong: Staying in S3 Standard does not address the cost driver (storage class pricing based on access frequency). “Compression at read time” is not an S3 lifecycle storage class optimization mechanism and would not directly lower S3 storage class charges as requested.
D
A policy that changes bucket encryption from SSE-S3 to SSE-KMS to reduce storage cost
Why wrong: Changing encryption type affects security and KMS key usage, not the fundamental S3 storage class pricing model. It is not a reliable method to reduce storage costs for infrequent access workloads.

Question 6mediummultiple 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?

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 7mediummultiple 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…

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 8mediummultiple choice

An S3 bucket stores user-uploaded media. Most objects are never read again, but compliance requires keeping them for at least 18 months. Retrieval is rare and typically only needed during investigations. The current design keeps everything in S3 Standard, increasing storage cost. Which configuration best optimizes cost while meeting the retention and rare-access requirements?

Trap 1: Move all objects to S3 Glacier Instant Retrieval immediately upon…

Glacier Instant Retrieval can be useful for frequent retrieval needs with low latency, but it is not the most cost-optimized option for data that is rarely accessed. Disabling lifecycle removes the ability to move older data to cheaper tiers.

Trap 2: Keep objects in S3 Standard but compress them with a custom process…

While compression may reduce object size, it introduces additional compute complexity and operational overhead. The biggest driver of storage cost is usually the storage class; transitioning to an archive tier provides a more direct and predictable cost reduction.

Trap 3: Enable S3 Intelligent-Tiering for all objects and delete any object…

Intelligent-Tiering can help when access patterns are unpredictable, but deleting objects after 24 hours directly violates the stated compliance requirement to retain data for at least 18 months.

A
Move all objects to S3 Glacier Instant Retrieval immediately upon upload and disable lifecycle policies.
Why wrong: Glacier Instant Retrieval can be useful for frequent retrieval needs with low latency, but it is not the most cost-optimized option for data that is rarely accessed. Disabling lifecycle removes the ability to move older data to cheaper tiers.
B
Use an S3 lifecycle policy to transition objects to S3 Glacier Deep Archive after 30 days, and expire them after 18 months.
Lifecycle policies can automatically move data to lower-cost storage classes after it becomes infrequently accessed. Because reads are rare and required only during investigations, Glacier Deep Archive is a strong cost-optimization choice. Setting expiration after 18 months ensures compliance retention is met.
C
Keep objects in S3 Standard but compress them with a custom process to reduce storage size.
Why wrong: While compression may reduce object size, it introduces additional compute complexity and operational overhead. The biggest driver of storage cost is usually the storage class; transitioning to an archive tier provides a more direct and predictable cost reduction.
D
Enable S3 Intelligent-Tiering for all objects and delete any object not accessed within 24 hours.
Why wrong: Intelligent-Tiering can help when access patterns are unpredictable, but deleting objects after 24 hours directly violates the stated compliance requirement to retain data for at least 18 months.

Question 9easymultiple choice

An S3 bucket stores application logs. After 30 days, the team rarely accesses the logs, but compliance requires keeping them for 18 months. Which setup most directly reduces storage cost while maintaining compliance?

Trap 1: Enable S3 Versioning and rely on deleting old versions after 30…

Versioning changes how objects are stored but does not inherently implement a deterministic “keep for 18 months” retention rule for all log data. You could still violate compliance if deletes/version retention are not aligned with the required retention window.

Trap 2: Move the bucket to a different AWS region farther from the users to…

S3 storage cost is not reduced by changing the distance to users, and changing regions can affect latency and operational complexity without providing a direct storage-cost reduction for the stated access pattern.

Trap 3: Switch all objects to S3 Glacier Instant Retrieval immediately,…

Applying the coldest tier to newly created (recent) logs increases cost if those objects are not actually infrequently accessed for the first 30 days. The scenario indicates the access pattern changes after 30 days.

A
Configure an S3 Lifecycle policy to transition objects to a colder storage class after 30 days and expire (delete) them after 18 months.
Lifecycle transitions lower the storage cost for older objects, and the expiration at 18 months enforces the compliance retention requirement.
B
Enable S3 Versioning and rely on deleting old versions after 30 days to reduce storage costs while keeping the latest data.
Why wrong: Versioning changes how objects are stored but does not inherently implement a deterministic “keep for 18 months” retention rule for all log data. You could still violate compliance if deletes/version retention are not aligned with the required retention window.
C
Move the bucket to a different AWS region farther from the users to reduce the likelihood of accidental reads and thereby lower storage costs.
Why wrong: S3 storage cost is not reduced by changing the distance to users, and changing regions can affect latency and operational complexity without providing a direct storage-cost reduction for the stated access pattern.
D
Switch all objects to S3 Glacier Instant Retrieval immediately, regardless of object age, to minimize storage charges.
Why wrong: Applying the coldest tier to newly created (recent) logs increases cost if those objects are not actually infrequently accessed for the first 30 days. The scenario indicates the access pattern changes after 30 days.