B

Question 1

Blob Storage access levels

Answer 1

Storage accounts support an additional access control mechanism that is limited to only Blob Storage. By default, no public read access is enabled for anonymous users, and only users w/ rights granted via RBAC or with the storage account name and key will have access to the stored blobs.
Private: only the storage account owner can access the container and its blobs.
Blob: only blobs within the container can be accessed anonymously.
Container: blobs and their containers can be accessed anonymously.

Question 2

Blob Storage access levels changes

Answer 2

You can change the access level through the Azure Portal, Azure Powershell, Azure CLI, REST API (programmatically) or Azure Storage Explorer. THE ACCESS LEVEL IS CONFIGURED SEPARATELY ON EACH BLOB CONTAINER.

Question 3

Blob Storage Network Access Level

Question 4

Blob types (How many different types)?

Answer 4

There are THREE different types.

1. Page Blobs - Optimized for random-access (read & write), stores virtual disk (VHD) files which using unmanaged disks w/ Azure an mostly used for log files. (MAX Page Blob is 8 TB).
2. Block Blobs - Optimized for efficient uploads/downloads for video, images (MAX Block Blob is 4.75 TB)
3. Append Blobs - Optimized for append operations (CANNOT UPDATE OR DELETE EXISTING BLOCKS WITHIN THE BLOB). Max of 50,000 blocks can be added to each Append Blob, each block can be up to 4 MB in size…giving a maximum Append Block of 195 GB.
   * *All THREE types can share a single blob container**

Question 5

Blob (True of False) - The type of blob is set at creation and cannot be changed after the fact?

Answer 5

True - you cannot change a blob after its created. Ex: IF a .vhd file was accidently uploaded as a Block Blob instead of a Page Blob. The blob would have to be deleted first and then reuploaded as a Page Blob before it can be mounted as an OS or data disk to an Azure VM.