A fjord-cabin photo album stores binary images with blob metadata in Azure. A teammate proposes Queue Storage or Azure SQL as the primary store because both are “Azure storage.” Which service selection matches Domain 2 for these objects?
Select an answer to reveal the explanation.
Short Explanation
Photos are crates of bytes—Blob Storage is the warehouse for that shape. Queues pass small work tickets; SQL stores structured rows. Calling everything “Azure storage” does not make Queue or SQL the right home for an image album.
Full Explanation
Domain 2 for AZ-204 centers on developing against Azure Storage for binary and object workloads—Azure Blob Storage is the service designed for large binary objects with associated blob metadata. A fjord-cabin photo album of images plus metadata belongs on Blob Storage: content in the blob body, descriptive properties in system/user metadata or index tags as needed. Calling other Azure services “storage” in the casual sense does not make them substitutes for the blob object store when the data shape is binary albums.
Storing each photo as a Queue Storage message fails because queues are for small control messages between producers and consumers, with strict size limits and ephemeral retention relative to durable object storage. Binary album primary storage is outside Queue Storage’s purpose.
Inserting JPEG bytes into Azure SQL rows as an official Blob substitute fails on cost, size limits, backup bloat, and API fit. SQL stores structured data; it is not the Blob Storage replacement for an image album.
Replacing Blob Storage with Azure Files only because photos are files fails as a forced swap. Azure Files is an SMB/NFS file share service valuable for lift-and-shift file shares; for app-owned object albums with blob APIs, SDKs, tiers, and lifecycle, Blob Storage remains the Domain 2 match unless a share protocol is explicitly required.
Exam caveat: “metadata” on blobs is not a relational schema—keep large searchable catalogs in an appropriate index if you outgrow metadata/tag limits. Operational check: upload one image as a block blob with user metadata, retrieve it with GetProperties/Download, and confirm the album path stays on Blob Storage rather than queues or SQL.