An otter-slide workflow needs sessions, transactions, and a dead-letter queue, but a teammate opens a storage-account queue because "a queue is a queue." Which service should the developer use?
Select an answer to reveal the explanation.
Short Explanation
Storage queues are fine for simple work — they are not sessions-plus-transactions-plus-DLQ. When the workflow needs that trio, pick Service Bus.
Full Explanation
Azure Queue Storage offers simple competing-consumer messaging with visibility timeouts but lacks Service Bus sessions, transactional message features, and a first-class dead-letter subqueue. Event Hubs and Microsoft Graph are not replacements for that Service Bus capability set.