Blob storage (block, append, page) in Azure - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Azure Blob Storage?

Azure Blob Storage is a service that stores large amounts of unstructured data like text or binary files. It is like a big online container where you can keep files accessible from anywhere.

beginner

What is a Block Blob in Azure Blob Storage?

A Block Blob stores text and binary data in blocks. It is good for files that change often, like documents or images. You upload blocks separately and then combine them into one blob.

intermediate

What is an Append Blob and when is it used?

An Append Blob is optimized for append operations, meaning you can only add data to the end. It is great for logging scenarios where new data is always added at the end.

intermediate

What is a Page Blob and what is it best for?

A Page Blob stores data in pages of 512 bytes and supports random read/write operations. It is ideal for virtual hard drives or scenarios needing frequent updates to parts of the data.

intermediate

How do Block, Append, and Page Blobs differ in usage?

Block Blobs are for general file storage, Append Blobs for adding data sequentially like logs, and Page Blobs for frequent random writes like virtual disks.

Which Azure Blob type is best for storing log files that grow by adding data at the end?

A Append Blob

B Page Blob

C Block Blob

D File Blob

Append Blob is designed for append operations, making it ideal for logs that grow by adding data at the end.

Which blob type supports random read and write operations in 512-byte pages?

A Queue Blob

B Append Blob

C Block Blob

D Page Blob

Page Blob stores data in 512-byte pages and supports random read/write, suitable for virtual disks.

What is the main use case for Block Blobs?

A Storing virtual hard drives

B Storing large files like images or documents

C Message queuing

D Appending log data

Block Blobs are optimized for storing large files such as images, videos, and documents.

Which blob type allows you to upload data in separate blocks and then commit them together?

A Page Blob

B Append Blob

C Block Blob

D Table Blob

Block Blob uploads data in blocks that can be committed together to form the final blob.

If you need to frequently update parts of a file randomly, which blob type should you choose?

A Page Blob

B Block Blob

C Append Blob

D File Blob

Page Blob supports random read/write operations, making it suitable for frequent partial updates.

Explain the differences between block, append, and page blobs in Azure Blob Storage.

Think about how data is added or updated in each blob type.

Describe a real-life scenario where you would use each type of Azure Blob Storage.

Match the blob type to the data access pattern.

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