Intermediate
Prepare and test your skills
Intermediate
Prepare and test your skills
Azure Blob System Properties and User-Defined Metadata
Free sample question, answered and explained below. The AZ-204 Developing Solutions for Microsoft Azure Exam practice bank has 1,929 more like it. Try 10 free: instant score, no account.
A development team is building an application that uploads various document types, such as PDFs and images, to Azure Blob Storage. For each uploaded document, they need to ensure that the browser correctly interprets the file type by setting the appropriate Content-Type property. Additionally, they must attach custom information, specifically a ProjectID and DocumentVersion, to each blob for internal tracking and categorization.
The team is using the Azure Blob Storage .NET SDK.
Which of the following approaches should the team use to efficiently set both the standard Content-Type and the custom ProjectID and DocumentVersion for each blob?
Explanations
Store Content-Type, ProjectID, and DocumentVersion all as user-defined metadata.
Store Content-Type, ProjectID, and DocumentVersion all as user-defined metadata.
While you can store custom data as user-defined metadata, Content-Type is a specific system property that directly impacts how web browsers and applications handle the blob. Storing it as user-defined metadata would prevent it from being recognized as a standard HTTP header, leading to incorrect interpretation of the file type. The documentation clearly separates 'System properties' from 'User-defined metadata,' indicating they are handled differently.
Utilize blob index tags for ProjectID and DocumentVersion, and set Content-Type as a system property.
Utilize blob index tags for ProjectID and DocumentVersion, and set Content-Type as a system property.
While blob index tags can store key-value attributes for categorization and searching, they are a distinct feature from user-defined metadata. The question specifically asks to attach 'custom information' as 'metadata' for internal tracking. User-defined metadata is designed for this purpose, offering simple key-value pairs that don't affect blob behavior. Blob index tags are primarily for creating a searchable index. The documentation notes: 'Blob index tags also provide the ability to store arbitrary user-defined key/value attributes alongside an Azure Blob storage resource.' This indicates they are an additional way to store attributes, not a replacement for user-defined metadata in this context.
Set the Content-Type using the blob's HTTP headers (system properties) and store ProjectID and DocumentVersion as user-defined metadata using a key-value dictionary.
Set the Content-Type using the blob's HTTP headers (system properties) and store ProjectID and DocumentVersion as user-defined metadata using a key-value dictionary.
Azure Blob Storage distinguishes between system properties, like Content-Type, which are standard HTTP headers, and user-defined metadata, which are custom key-value pairs. The most efficient and correct approach is to use the .NET SDK's capabilities to set the Content-Type as a system property (e.g., via BlobHttpHeaders) and to set ProjectID and DocumentVersion as user-defined metadata (e.g., via a Dictionary<string, string>). This ensures proper handling by browsers for Content-Type and provides flexible, accessible custom tracking information without affecting blob behavior. The documentation states: 'System properties exist on each Blob storage resource. Some of them can be read or set, while others are read-only. Under the covers, some system properties correspond to certain standard HTTP headers.' and 'User-defined metadata consists of one or more name-value pairs that you specify for a Blob storage resource. You can use metadata to store additional values with the resource.'
Set Content-Type as a system property and embed ProjectID and DocumentVersion within the blob's content as JSON.
Set Content-Type as a system property and embed ProjectID and DocumentVersion within the blob's content as JSON.
Embedding custom tracking information like ProjectID and DocumentVersion directly within the blob's content as JSON is generally inefficient for metadata purposes. This approach would require downloading and parsing the entire blob content to retrieve these values, which is resource-intensive compared to accessing them directly as blob metadata. Azure Blob Storage provides dedicated mechanisms for metadata that are designed for this type of external tracking information. The documentation highlights that 'User-defined metadata consists of one or more name-value pairs that you specify for a Blob storage resource. You can use metadata to store additional values with the resource.'
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 1,929 practice questions across all 5 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Monitor Metrics Explorer
Describe the Azure portal
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Software as a Service (SaaS)
Describe software as a service (SaaS)
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure VM Stopped Deallocated Disk Billing
Describe factors that can affect costs in Azure
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Microsoft Entra B2B Collaboration with Conditional Access
Describe external identities in Azure
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Microsoft Defender for Cloud CSPM
Describe the purpose of Microsoft Defender for Cloud
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Data Box Heavy vs Data Box
Describe migration options, including Azure Migrate and Azure Data Box
Last updated