What if you never had to worry about losing or juggling your important files again?
Why Blob storage (S3, Azure Blob) in HLD? - Purpose & Use Cases
Imagine you have hundreds of photos, videos, and documents saved on your computer's hard drive. You want to share them with friends or access them from anywhere, but you have to manually copy files to USB drives or email them one by one.
This manual way is slow and risky. Files can get lost, corrupted, or accidentally deleted. Sharing large files is hard, and you can't easily control who sees what. Plus, your computer's storage fills up fast, and backups are a headache.
Blob storage services like S3 or Azure Blob let you store all your files safely in the cloud. You can upload, organize, and access them anytime from any device. The cloud handles backups, security, and scaling automatically, so you don't have to worry about losing data or running out of space.
Copy files manually to USB or email attachmentsUse cloud commands or web portals to upload and manage files in blob storage
It makes storing and sharing large amounts of files easy, safe, and accessible from anywhere in the world.
A photographer uploads thousands of high-resolution photos to S3, then shares links with clients without sending huge files by email.
Manual file sharing is slow and risky.
Blob storage offers safe, scalable cloud storage.
Access and share files easily from anywhere.
Practice
Solution
Step 1: Understand blob storage function
Blob storage is designed to save large files like videos, images, and backups in the cloud.Step 2: Compare with other cloud services
Other services like virtual machines or identity management serve different purposes, not file storage.Final Answer:
To store large files safely and accessibly in the cloud -> Option CQuick Check:
Blob storage = large file storage [OK]
- Confusing blob storage with compute services
- Thinking blob storage manages users
- Assuming blob storage hosts websites directly
Solution
Step 1: Review S3 bucket naming rules
S3 bucket names must be lowercase, can include hyphens, but no underscores or special characters like '!'.Step 2: Check each option
my-bucket-name uses lowercase letters and hyphens, which is valid. Options A, B, and C are invalid: A has uppercase letters and dots, B has uppercase and '!', C has underscores.Final Answer:
my-bucket-name -> Option DQuick Check:
Bucket names use lowercase and hyphens [OK]
- Using uppercase letters in bucket names
- Including underscores or special characters
- Using dots in bucket names
aws s3 cp file.txt s3://my-bucket/ --storage-class STANDARD_IAWhat does the
--storage-class STANDARD_IA option do?Solution
Step 1: Understand storage classes in S3
STANDARD_IA means Standard-Infrequent Access, a cheaper tier for files accessed less often.Step 2: Analyze command effect
The command uploads file.txt to the bucket using this storage class, saving cost for infrequent access.Final Answer:
Uploads the file to a cheaper, infrequently accessed storage tier -> Option AQuick Check:
STANDARD_IA = cheaper, infrequent access [OK]
- Thinking it encrypts the file
- Assuming it makes file public
- Confusing with multi-region redundancy
Solution
Step 1: Recall Azure container naming rules
Container names must be lowercase letters and numbers only, no uppercase letters allowed.Step 2: Match error cause
An invalid container name error usually means the name breaks these rules, such as having uppercase letters.Final Answer:
The container name contains uppercase letters -> Option AQuick Check:
Azure container names must be lowercase [OK]
- Blaming file size for container name errors
- Confusing region with naming rules
- Thinking file name affects container name
Solution
Step 1: Understand storage classes and lifecycle
STANDARD_IA offers cheaper storage with quick access. GLACIER is very cheap but slow to retrieve.Step 2: Analyze cost and access needs
Using STANDARD_IA first allows quick access. Moving to GLACIER after 30 days saves cost for older backups.Step 3: Evaluate other options
GLACIER only delays access too much. STANDARD is costly. REDUCED_REDUNDANCY is deprecated and less reliable.Final Answer:
Use STANDARD_IA storage class with lifecycle rule to move files to GLACIER after 30 days -> Option BQuick Check:
STANDARD_IA + lifecycle to GLACIER = cost + access balance [OK]
- Choosing GLACIER only and ignoring access speed
- Enabling public access unnecessarily
- Using deprecated REDUCED_REDUNDANCY class
Ready to prove it?
Pass the test and this pattern moves unknown
