S3 storage class optimization in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding S3 Storage Classes for Cost Efficiency

You have a dataset that is accessed frequently for the first 30 days after upload, then rarely accessed but must be retained for years. Which S3 storage class is the best fit to optimize cost while meeting access needs?

A S3 Intelligent-Tiering with automatic tiering between frequent and infrequent access

B S3 One Zone-Infrequent Access for all data

C S3 Glacier Deep Archive immediately after upload

D S3 Standard for all data retention period

💡 Hint

Think about a storage class that adapts automatically to changing access patterns.

S3 Intelligent-Tiering automatically moves data between frequent and infrequent access tiers based on usage, optimizing cost without performance impact. Using Standard all the time is costly. Glacier Deep Archive is for long-term archival and has retrieval delays. One Zone-IA risks data loss and is not ideal for critical data.

❓ Architecture

intermediate

Designing Lifecycle Policies for S3 Data

You want to automate moving objects from S3 Standard to S3 Glacier after 60 days and then delete them after 2 years. Which lifecycle policy configuration achieves this?

A Transition to Glacier after 60 days; No expiration

B Transition to Glacier after 730 days; Expire after 60 days

C Expire after 60 days; Transition to Glacier after 730 days

D Transition to Glacier after 60 days; Expire after 730 days

💡 Hint

Think about the order: first move to cheaper storage, then delete later.

The lifecycle policy should first transition objects to Glacier after 60 days to save cost, then expire (delete) them after 730 days (2 years). Option D correctly sets this order. Other options either delete too early or transition too late.

❓ security

advanced

Securing S3 Data with Storage Class and Access Controls

You have sensitive data stored in S3 Glacier Deep Archive. You want to ensure only authorized users can restore and access this data. Which combination of settings best enforces this?

A Use bucket policies to restrict restore actions and enable encryption with AWS KMS

B Disable all encryption and rely on IAM roles only

C Use public read ACLs and rely on storage class for security

D Allow all users to restore but restrict download via VPC endpoint policies

💡 Hint

Think about combining encryption and access policies for sensitive data.

Bucket policies restricting restore actions combined with encryption using AWS KMS provide strong security controls. Public read ACLs expose data. Disabling encryption weakens security. Allowing all users to restore risks unauthorized access.

❓ service_behavior

advanced

S3 Intelligent-Tiering Behavior on Access Patterns

You upload objects to S3 Intelligent-Tiering. After 45 days, some objects are not accessed at all. What happens to these objects automatically?

A Objects are deleted automatically after 30 days

B Objects remain in the frequent access tier indefinitely

C Objects are moved to the infrequent access tier to reduce cost

D Objects are moved to Glacier Deep Archive immediately

💡 Hint

Consider how Intelligent-Tiering optimizes cost based on usage.

S3 Intelligent-Tiering monitors access and moves objects not accessed for 30 consecutive days to the infrequent access tier automatically to save cost. It does not delete objects or move them to Glacier Deep Archive immediately.

✅ Best Practice

expert

Optimizing S3 Storage Costs for Large, Rarely Accessed Data Sets

Your company stores petabytes of data that are rarely accessed but must be retained for compliance. You want to minimize storage costs while ensuring data durability and occasional retrieval within hours. Which storage class and strategy best meet these requirements?

A Use S3 Standard storage class only to avoid retrieval delays

B Use S3 Glacier Flexible Retrieval with lifecycle policy transitioning data after 30 days from Standard

C Use S3 Glacier Deep Archive with no lifecycle transitions and retrieve data on demand

D Use S3 One Zone-Infrequent Access for all data to save cost

💡 Hint

Think about balancing cost, durability, and retrieval time.

S3 Glacier Flexible Retrieval offers low cost with retrieval times in minutes to hours, suitable for rarely accessed data with compliance needs. Transitioning data after 30 days reduces cost. Standard is costly for large data. Glacier Deep Archive has longer retrieval times (up to 12 hours). One Zone-IA lacks multi-AZ durability.

Practice

1. What is the main benefit of using S3 storage class optimization in AWS?

easy

A. It increases the speed of data retrieval from S3 buckets.

B. It creates backups of S3 data in multiple regions.

C. It automatically encrypts all files stored in S3.

D. It reduces storage costs by moving data to cheaper classes based on usage.

Solution

1. Step 1: Understand the purpose of storage class optimization

   S3 storage class optimization is designed to save money by moving data to cheaper storage classes when it is less frequently accessed.

2. Step 2: Compare options to the purpose

   Only It reduces storage costs by moving data to cheaper classes based on usage. describes cost saving by moving data based on usage. Other options describe different features not related to storage class optimization.

3. Final Answer:

   It reduces storage costs by moving data to cheaper classes based on usage. -> Option D

4. Quick Check:

   Cost saving by data movement = B [OK]

Hint: Focus on cost saving by data movement between storage classes [OK]

Common Mistakes:

• Confusing optimization with encryption or backup features
• Thinking it improves retrieval speed primarily
• Assuming it automatically creates backups

2. Which of the following is the correct syntax to create a lifecycle rule in an S3 bucket to transition objects to the STANDARD_IA storage class after 30 days?

easy

A. {"Rules": [{"Status": "Enabled", "Transitions": [{"Day": 30, "StorageClass": "STANDARD_IA"}]}]}

B. {"Rules": [{"Status": "Enabled", "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}]}]}

C. {"Rules": [{"Status": "Active", "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}]}]}

D. {"Rules": [{"Status": "Enabled", "Transition": [{"Days": 30, "StorageClass": "STANDARD_IA"}]}]}

Solution

1. Step 1: Identify correct lifecycle rule syntax

   The correct key for multiple transitions is "Transitions" (plural), and the status must be "Enabled" to activate the rule.

2. Step 2: Check each option for syntax errors

   {"Rules": [{"Status": "Enabled", "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}]}]} uses "Transitions" and "Status": "Enabled" correctly. {"Rules": [{"Status": "Enabled", "Transition": [{"Days": 30, "StorageClass": "STANDARD_IA"}]}]} uses "Transition" (singular) which is invalid. {"Rules": [{"Status": "Active", "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}]}]} uses "Status": "Active" which is incorrect. {"Rules": [{"Status": "Enabled", "Transitions": [{"Day": 30, "StorageClass": "STANDARD_IA"}]}]} uses "Day" instead of "Days" which is invalid.

3. Final Answer:

   {"Rules": [{"Status": "Enabled", "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}]}]} -> Option B

4. Quick Check:

   Correct lifecycle JSON syntax = D [OK]

Hint: Remember plural 'Transitions' and 'Status' must be 'Enabled' [OK]

Common Mistakes:

• Using singular 'Transition' instead of 'Transitions'
• Setting status to 'Active' instead of 'Enabled'
• Using 'Day' instead of 'Days' key

3. Given this lifecycle rule JSON snippet, what will happen to objects older than 60 days?

{"Rules": [{"Status": "Enabled", "Transitions": [{"Days": 30, "StorageClass": "STANDARD_IA"}, {"Days": 60, "StorageClass": "GLACIER"}]}]}

medium

A. Objects older than 60 days will be deleted automatically.

B. Objects older than 60 days will remain in STANDARD_IA storage class.

C. Objects older than 60 days will be moved to GLACIER storage class.

D. Objects older than 60 days will be moved back to STANDARD storage class.

Solution

1. Step 1: Analyze the lifecycle transitions

   The rule transitions objects to STANDARD_IA after 30 days, then to GLACIER after 60 days.

2. Step 2: Determine final storage class after 60 days

   Objects older than 60 days will be moved to GLACIER, which is a colder, cheaper storage class.

3. Final Answer:

   Objects older than 60 days will be moved to GLACIER storage class. -> Option C

4. Quick Check:

   Lifecycle transitions move objects to GLACIER after 60 days = A [OK]

Hint: Check the last transition day and storage class [OK]

Common Mistakes:

• Thinking objects stay in STANDARD_IA after 60 days
• Confusing transition with deletion
• Assuming objects move back to STANDARD

4. A user created this lifecycle rule but objects are not transitioning to GLACIER after 90 days:

{"Rules": [{"Status": "Enabled", "Transitions": [{"Days": 90, "StorageClass": "GLACIER"}], "Expiration": {"Days": 365}}]}

What is the most likely reason?

medium

A. The rule is missing a filter to specify which objects to apply to.

B. GLACIER storage class is deprecated and cannot be used.

C. The Expiration setting prevents transitions to GLACIER.

D. The 'Days' value must be less than 30 for transitions.

Solution

1. Step 1: Check lifecycle rule requirements

   Lifecycle rules require a filter or prefix to specify which objects the rule applies to. Without a filter, the rule may not apply to any objects.

2. Step 2: Evaluate other options

   GLACIER is still valid, expiration does not block transitions, and 'Days' can be any positive number.

3. Final Answer:

   The rule is missing a filter to specify which objects to apply to. -> Option A

4. Quick Check:

   Missing filter causes no transitions = A [OK]

Hint: Always include a filter or prefix in lifecycle rules [OK]

Common Mistakes:

• Assuming GLACIER is deprecated
• Thinking expiration blocks transitions
• Believing 'Days' must be under 30

5. You manage a large S3 bucket with mixed access patterns. You want to optimize costs by automatically moving files to cheaper storage classes but keep frequently accessed files in STANDARD. Which lifecycle rule setup best achieves this?

hard

A. Transition objects to STANDARD_IA after 30 days and to GLACIER after 90 days, with a filter excluding files accessed in last 30 days.

B. Transition all objects to GLACIER immediately after upload to save costs.

C. Delete objects after 30 days to save storage costs.

D. Keep all objects in STANDARD storage class to ensure fastest access.

Solution

1. Step 1: Understand access patterns and cost goals

   Frequently accessed files should stay in STANDARD. Less accessed files should move to cheaper classes like STANDARD_IA and GLACIER.

2. Step 2: Evaluate lifecycle rule options

   Transition objects to STANDARD_IA after 30 days and to GLACIER after 90 days, with a filter excluding files accessed in last 30 days. uses transitions with a filter to exclude recently accessed files, optimizing costs while keeping frequent files fast. Transition all objects to GLACIER immediately after upload to save costs. moves all files immediately to GLACIER, causing slow access. Delete objects after 30 days to save storage costs. deletes files, which may lose data. Keep all objects in STANDARD storage class to ensure fastest access. keeps all files in STANDARD, not optimizing costs.

3. Final Answer:

   Transition objects to STANDARD_IA after 30 days and to GLACIER after 90 days, with a filter excluding files accessed in last 30 days. -> Option A

4. Quick Check:

   Use transitions with filters to balance cost and access = C [OK]

Hint: Use filters to exclude recent files from transitions [OK]

Common Mistakes:

• Moving all files to GLACIER immediately
• Deleting files instead of transitioning
• Keeping all files in expensive STANDARD class