A herring-smoke house stores Content-Type and a custom smoker-bay label on the same Azure blob. How should the developer treat those two pieces of information in the Blob SDK?
Select an answer to reveal the explanation.
Short Explanation
HTTP headers like Content-Type are the blob’s system nameplate; smoker-bay is a sticky note you wrote yourself. Properties and user metadata are two different SDK knobs on the same blob. Do not mash them into one bag.
Full Explanation
Azure Blob Storage distinguishes system properties (Content-Type, Cache-Control, ETag, and related HTTP headers) from user-defined metadata name-value pairs. The SDK exposes separate APIs for setting and retrieving each surface. Index tags and ACLs are different features; Cosmos is unrelated to this Blob properties-and-metadata skill.