A xeric-wash study plan files Azure Storage queues under Cosmos and Blob skills. Where do Storage queues belong on the AZ-204 outline?
Select an answer to reveal the explanation.
Short Explanation
Cosmos and Blob live in Domain 2. Storage queues are messaging — park them in Domain 5 with the other queues and buses.
Full Explanation
On the AZ-204 outline, Azure Queue Storage belongs with Domain 5 message-based solutions alongside Event Grid, Event Hubs, and Service Bus. A xeric-wash study plan that files Storage queues under Cosmos and Blob skills misplaces them: Domain 2 emphasizes Cosmos DB and Blob Storage SDK work, while Storage queues are assessed as messaging—competing consumers, visibility timeout, poison handling, and size limits—not as general-purpose storage APIs.
Filing them as Domain 2 storage beside Cosmos SDK partitioning labs fails because partitioning labs and Blob SDK skills are not the messaging objectives for Storage queues. Domain 4 Application Insights live metrics only fails conceptually: monitoring is Domain 4; it does not redefine where queues sit in the outline. Domain 3 Microsoft Graph mailbox permissions fail because Graph/identity content is separate from Domain 5 message-based solutions.
Exam caveat: outlines can regroup skills across exam updates—always verify the current skills measured document, but do not conflate Blob storage with Storage queues as the same domain task. Operational check: when reviewing a study map, place Storage queue scenarios next to Service Bus/Event Hubs selection questions and practice visibility timeout and dequeue-count poison handling there.