Blob storage (block, append, page) in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Blob Types for Different Use Cases

Which Azure Blob storage type is best suited for scenarios where you need to frequently append data, such as logging or auditing?

A Append Blob

B Block Blob

C Page Blob

D File Blob

💡 Hint

Think about which blob type is optimized for adding data at the end without rewriting the entire blob.

Append Blob is designed specifically for append operations, making it ideal for logs and audit trails where data is added sequentially.

❓ service_behavior

intermediate

Page Blob Size Behavior

What happens if you try to write data beyond the current size of a Page Blob in Azure Blob Storage?

A The blob automatically expands to accommodate the new data.

B An error is returned because writes must be within the allocated size.

C The data is truncated to fit the current blob size.

D The blob converts to a Block Blob to allow the write.

💡 Hint

Consider how Page Blobs manage storage allocation and writes.

Page Blobs require pre-allocated size and writes must be within this size. Writing beyond causes an error.

❓ Configuration

advanced

Configuring Blob Storage for Large File Uploads

You want to upload a 200 GB file to Azure Blob Storage efficiently. Which blob type and upload method combination is the best practice?

A Use Block Blob with Put Block and Put Block List operations to upload in chunks.

B Use Append Blob with multiple Append Block operations.

C Use Block Blob with Put Blob operation in a single request.

D Use Page Blob with random writes to upload the file sequentially.

💡 Hint

Think about how to upload large files in parts efficiently.

Block Blobs support chunked uploads using Put Block and Put Block List, which is efficient for large files.

❓ security

advanced

Securing Append Blob for Audit Logs

Which security feature should you enable to ensure that audit logs stored in Append Blobs cannot be modified or deleted once written?

A Enable Soft Delete on the storage account.

B Enable Shared Access Signature (SAS) with write permissions.

C Enable Azure Defender for Storage.

D Enable Immutable Blob Storage with Time-based retention policy.

💡 Hint

Consider how to make blobs unchangeable after creation.

Immutable Blob Storage with retention policies ensures data cannot be modified or deleted during the retention period, ideal for audit logs.

❓ Architecture

expert

Designing a High-Performance VM Disk Storage Solution

You need to design a storage solution for Azure Virtual Machines that require frequent random read/write operations with low latency. Which blob type should you use and why?

A Use Append Blob because it allows efficient appending of data.

B Use Block Blob because it supports large files and efficient uploads.

C Use Page Blob because it supports random read/write operations with low latency.

D Use File Blob because it supports SMB protocol for VM disks.

💡 Hint

Think about the storage type Azure uses for VM disks and their access patterns.

Page Blobs are used for Azure VM disks because they support random read/write with low latency, which is essential for VM performance.

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