Why Blob storage (block, append, page) in Azure? - Purpose & Use Cases

The Big Idea

What if you could never lose data or restart uploads, no matter how big your files grow?

The Scenario

Imagine you have a huge collection of photos, videos, and documents saved on your computer. You want to share them with friends or keep them safe, but your hard drive is full and organizing files manually is a mess.

Or think about trying to add new information to a log file every minute without losing anything or slowing down your system.

The Problem

Manually managing large files or logs on local storage is slow and risky. You might accidentally overwrite files, lose data, or run out of space. Uploading big files in one go can fail and force you to start over.

Appending data to files manually is tricky and error-prone, especially when many users try to write at the same time.

The Solution

Blob storage in the cloud breaks files into smaller pieces called blocks, pages, or append blobs. This lets you upload, update, or add data efficiently without starting from scratch.

Block blobs are great for large files uploaded in parts. Append blobs let you add data continuously, perfect for logs. Page blobs support fast random reads and writes, ideal for virtual disks.

Before vs After

✗ Before

Open file
Write entire content
Close file

✓ After

Upload blocks
Commit blocks
Append new data

What It Enables

It makes storing, updating, and scaling large files or logs easy, reliable, and fast in the cloud.

Real Life Example

A company collects millions of sensor readings every day. Using append blobs, they add new data continuously without losing any information or slowing down their system.

Key Takeaways

Manual file handling is slow and risky for big or growing data.

Blob storage types fit different needs: block for big files, append for logs, page for fast random access.

Cloud blobs make data storage scalable, safe, and efficient.

Practice

1. Which type of Azure Blob storage is best suited for storing large files that are uploaded in blocks and can be updated by replacing blocks?

easy

A. Append blob

B. Page blob

C. Block blob

D. File blob

Solution

1. Step 1: Understand block blob usage

   Block blobs are designed to store large files uploaded in blocks and allow updating by replacing blocks.

2. Step 2: Compare with other blob types

   Append blobs are for append-only operations, and page blobs are optimized for random read/write operations, not block uploads.

3. Final Answer:

   Block blob -> Option C

4. Quick Check:

   Block blob = large files in blocks [OK]

Hint: Block blobs store large files in blocks, perfect for uploads [OK]

Common Mistakes:

• Confusing append blob with block blob
• Thinking page blob is for block uploads
• Selecting non-existent blob types

2. Which of the following is the correct way to create an append blob using Azure CLI?

easy

A. az storage blob create --container-name mycontainer --name myappendblob --type AppendBlob

B. az storage blob create --container-name mycontainer --name myappendblob --type BlockBlob

C. az storage blob create --container-name mycontainer --name myappendblob --type PageBlob

D. az storage blob create --container-name mycontainer --name myappendblob --type FileBlob

Solution

1. Step 1: Identify correct blob type syntax

   The Azure CLI uses --type AppendBlob to create an append blob.

2. Step 2: Verify other options

   BlockBlob and PageBlob are valid types but not for append blobs; FileBlob is invalid.

3. Final Answer:

   az storage blob create --container-name mycontainer --name myappendblob --type AppendBlob -> Option A

4. Quick Check:

   Append blob creation uses --type AppendBlob [OK]

Hint: Use --type AppendBlob to create append blobs in Azure CLI [OK]

Common Mistakes:

• Using BlockBlob type for append blobs
• Using PageBlob type for append blobs
• Using invalid blob type names

3. Consider this code snippet using Azure SDK to upload data to a blob:

blob_client = container_client.get_blob_client('myblob')
blob_client.upload_blob(data, blob_type='PageBlob')

What will happen if the data size is not a multiple of 512 bytes?

medium

A. Upload will fail with an error about data size alignment

B. Upload will succeed with data padded to 512-byte boundaries

C. Upload will succeed but truncate extra bytes

D. Upload will convert data to block blob automatically

Solution

1. Step 1: Understand page blob requirements

   Page blobs require data size to be a multiple of 512 bytes for alignment.

2. Step 2: Analyze upload behavior

   If data size is not aligned, the upload will fail with an error about size alignment.

3. Final Answer:

   Upload will fail with an error about data size alignment -> Option A

4. Quick Check:

   Page blob data size must be multiple of 512 bytes [OK]

Hint: Page blobs need 512-byte aligned data size [OK]

Common Mistakes:

• Assuming automatic padding of data
• Thinking upload truncates data silently
• Believing blob type auto-conversion occurs

4. You have an append blob but your application tries to overwrite existing data instead of appending. What is the likely cause and fix?

medium

A. Using page blob API calls on append blob

B. Using append_block method instead of upload_blob

C. Creating the blob as a block blob instead of append blob

D. Using upload_blob with overwrite=True instead of append_block method

Solution

1. Step 1: Identify append blob usage

   Append blobs require using append_block to add data without overwriting.

2. Step 2: Analyze the overwrite behavior

   Using upload_blob with overwrite=True replaces existing data, not appends.

3. Final Answer:

   Using upload_blob with overwrite=True instead of append_block method -> Option D

4. Quick Check:

   Append blobs append with append_block, not upload_blob overwrite [OK]

Hint: Use append_block to add data, not upload_blob overwrite [OK]

Common Mistakes:

• Confusing append_block and upload_blob methods
• Creating wrong blob type
• Using page blob APIs on append blobs

5. You need to design a system that stores virtual machine disks requiring frequent random read/write operations with low latency. Which Azure blob type should you choose and why?

hard

A. Append blob, because it allows efficient appending of logs

B. Page blob, because it supports random read/write with 512-byte pages

C. Block blob, because it supports large file uploads in blocks

D. File blob, because it supports file system semantics

Solution

1. Step 1: Identify requirements for VM disks

   VM disks need frequent random read/write with low latency and page-level updates.

2. Step 2: Match blob type to requirements

   Page blobs support random read/write operations in 512-byte pages, ideal for VM disks.

3. Step 3: Exclude other blob types

   Block blobs are for large uploads, append blobs for append-only logs, and file blob is not a valid Azure blob type.

4. Final Answer:

   Page blob, because it supports random read/write with 512-byte pages -> Option B

5. Quick Check:

   VM disks use page blobs for random read/write [OK]

Hint: Page blobs support random read/write, perfect for VM disks [OK]

Common Mistakes:

• Choosing block blob for VM disks
• Confusing append blob with page blob
• Selecting non-existent file blob type