Develop solutions that use Blob storage

Question 1

Blob storage is designed for

Answer 1

Serving images or documents directly to a browser.
Storing files for distributed access.
Streaming video and audio.
Writing to log files.
Storing data for backup and restore, disaster recovery, and archiving.
Storing data for analysis by an on-premises or Azure-hosted service.

Question 2

Access tiers for block blob data

Answer 2

Hot access tier
Cool access tier
Cold access tier
Archive tier

Question 3

Hot access tier

Answer 3

The Hot access tier, which is optimized for frequent access of objects in the storage account. The Hot tier has the highest storage costs, but the lowest access costs. New storage accounts are created in the hot tier by default.

Question 4

Cool access tier

Answer 4

The Cool access tier, which is optimized for storing large amounts of data that is infrequently accessed and stored for a minimum of 30 days. The Cool tier has lower storage costs and higher access costs compared to the Hot tier.

Question 5

Cold access tier

Answer 5

The Cold access tier, which is optimized for storing data that is infrequently accessed and stored for a minimum of 90 days. The cold tier has lower storage costs and higher access costs compared to the cool tier.

Question 6

Archive tier

Answer 6

The Archive tier, which is available only for individual block blobs. The archive tier is optimized for data that can tolerate several hours of retrieval latency and remains in the Archive tier for a minimum 180 days. The archive tier is the most cost-effective option for storing data, but accessing that data is more expensive than accessing data in the hot or cool tiers.

Question 7

Blob storage offers three types of resources:

Answer 7

The storage account.
A container in the storage account
A blob in a container

Question 8

the default endpoint for Blob storage is:

Answer 8

http://mystorageaccount.blob.core.windows.net

Question 9

rules when naming a container:

Answer 9

Container names can be between 3 and 63 characters long.
Container names must start with a letter or number, and can contain only lowercase letters, numbers, and the dash (-) character.
Two or more consecutive dash characters aren’t permitted in container names.

Question 10

The URI for a container is similar to:

Answer 10

https://myaccount.blob.core.windows.net/mycontainer

Question 11

Blobs - Azure Storage supports three types of blobs:

Answer 11

Block blobs store text and binary data. Block blobs are made up of blocks of data that can be managed individually. Block blobs can store up to about 190.7 TiB.

Append blobs are made up of blocks like block blobs, but are optimized for append operations. Append blobs are ideal for scenarios such as logging data from virtual machines.

Page blobs store random access files up to 8 TB in size. Page blobs store virtual hard drive (VHD) files and serve as disks for Azure virtual machines.

Question 12

The URI for a blob is similar to:

Answer 12

https://myaccount.blob.core.windows.net/mycontainer/myblob

or

https://myaccount.blob.core.windows.net/mycontainer/myvirtualdirectory/myblob

Question 13

data lifecycle management policy

Answer 13

Transition blobs from cool to hot immediately when accessed, to optimize for performance.

Transition current versions of a blob, previous versions of a blob, or blob snapshots to a cooler storage tier if these objects aren’t accessed or modified for a period of time, to optimize for cost.

Delete current versions of a blob, previous versions of a blob, or blob snapshots at the end of their lifecycles.

Apply rules to an entire storage account, to select containers, or to a subset of blobs using name prefixes or blob index tags as filters.

Question 14

Rule filters

Answer 14

blobTypes - An array of predefined enum values.
prefixMatch - An array of strings for prefixes to be match. Each rule can define up to 10 prefixes. A prefix string must start with a container name.
blobIndexMatch - An array of dictionary values consisting of blob index tag key and value conditions to be matched. Each rule can define up to 10 blob index tag condition.

Question 15

Rule actions

Answer 15

tierToCool
tierToCold
enableAutoTierToHotFromCool
tierToArchive
delete

Question 16

If you define more than one action on the same blob

Answer 16

If you define more than one action on the same blob, lifecycle management applies the least expensive action to the blob. For example, action delete is cheaper than action tierToArchive. Action tierToArchive is cheaper than action tierToCool.

Question 17

Action run condition

Answer 17

daysAfterModificationGreaterThan
daysAfterCreationGreaterThan (snapshot)
daysAfterLastAccessTimeGreaterThan
daysAfterLastTierChangeGreaterThan (only for moving to Archive tier)

Question 18

You can add, edit, or remove Blob storage lifecycle policies by using any of the following methods:

Answer 18

Azure portal
Azure PowerShell
Azure CLI
REST APIs

Question 19

There are two options for rehydrating a blob that is stored in the archive tier:

Answer 19

Copy an archived blob to an online tier: You can rehydrate an archived blob by copying it to a new blob in the hot or cool tier with the Copy Blob or Copy Blob from URL operation. Microsoft recommends this option for most scenarios.

Change a blob’s access tier to an online tier: You can rehydrate an archived blob to hot or cool by changing its tier using the Set Blob Tier operation.

Question 20

Rehydration priority

Answer 20

Standard priority: The rehydration request is processed in the order it was received and might take up to 15 hours.
High priority: The rehydration request is prioritized over standard priority requests and might complete in under one hour for objects under 10 GB in size.

Question 21

To check the rehydration priority while the rehydration operation is underway

Answer 21

call Get Blob Properties to return the value of the x-ms-rehydrate-priority header. The rehydration priority property returns either Standard or High.

Question 22

packages contain the classes used to work with Blob Storage data resources:

Answer 22

Azure.Storage.Blobs: Contains the primary classes (client objects) that you can use to operate on the service, containers, and blobs.
Azure.Storage.Blobs.Specialized: Contains classes that you can use to perform operations specific to a blob type, such as block blobs.
Azure.Storage.Blobs.Models: All other utility classes, structures, and enumeration types.

Question 23

Create a client object

Answer 23

BlobServiceClient: Represents the client used to interact with the entire Azure Blob Storage account, allowing operations like listing containers or configuring account-level settings.

BlobContainerClient: Represents the client for a specific container within an Azure Blob Storage account, allowing operations like uploading, listing, or managing blobs within that container.

BlobClient: Represents the client for interacting with an individual blob in a container, enabling operations like uploading, downloading, or deleting that specific blob.

Question 24

The standard HTTP headers supported on blobs include:

Answer 24

ETag
Last-Modified
Content-Length
Content-Type
Content-MD5
Content-Encoding
Content-Language
Cache-Control
Origin
Range