Work with Azure Blob Storage

Question 1

What are azure client libraries?

Answer 1

• offer interface for making calls to AZ storage
• latest version is 12.x

Question 2

What classes do the az client libraries include?

Answer 2

• BlobServiceClient = represents SA
• BlobContainerClient = represents specific container
• BlobClient = represents specififc blob
• AppendBlobClient = append blob
• BlockBlocClient = block blob

Question 3

What packages container the classes used to work with blob storage data resources?

Answer 3

• Azure.Storage.Blobs = primary classes that you can use to operate on the service, containers and blobs
• Azure.Storage.Blobs.Specialised = classes that you can use to perform operations specific to a blob type such as block blobs
• Azure.Storage,Blobs.Models = utility classes, enums etc

Question 4

What is a client object?

Answer 4

• Working with any AZ resource using the SDK starts with creating client object
• you pass a URI referencing the endpoint to the client ctor
• endpoint can be constructed manually or queried for at runtime

Question 5

What are system properties in blob containers?

Answer 5

• exist on each blob storage resource
• read, set or read only
• some properties correspond to certain standard HTTP headers
• client library for .NET maintains properties for you

Question 6

What is user defined metadata for blob containers?

Answer 6

• one or more name-value pairs that you specify for blob storage resource
• can store additional values with the resource
• for your own purposes only and do not affect how resource behaves

Question 7

What rules must metadata name/value pairs adhere to?

Answer 7

• valid HTTP headers so should adhere to all restrictions governing headers
• must be valid HTTP header names and valid C# identifiers
• may contain only ASCII chars and should be treated as case-insensitive
• can contain non ASCII chars if they are base64 or URL encoded

Question 8

How can metadata headers be set on REST APIs?

Answer 8

• Can be set on a request that creates a new container or blob resource or on a request that explicitly creates a property on an existing resource
• total size of all pairs can be up to 8KB
• can only be read or written to in full, no partial updates
• GET/HEAD operation returns headers for specified container or blob
• PUT sets metadata on resource, overwriting existing metadata and if its called without any headers on the request it clears all existing metadata on the resource

Question 9

What is the difference between standard HTTP properties and metadata?

Answer 9

• metadata headers are named with prefix x-ms-meta- and a custom nameW

Question 10

What standard HTTP properties are supported on containers?

Answer 10

• Etag
• Last-modified

Question 11

What standard HTTP properties are supported on blobs?

Answer 11

• Etag
• Last-modified
• content-length
• content-type
  -content-MD5
• content-encoding
• content-language
  -cache-control
  -origin
  -range