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.