A city open-data team wants blobs for documents and queues for async job messages under one Azure Storage setup. What should they understand about a storage account?
Select an answer to reveal the explanation.
Short Explanation
One account can be a Swiss Army knife—blob endpoint here, queue endpoint there, same namespace roof. The open-data team does not need a new subscription for every service. Queues and tables are storage services too, not orphans outside the account.
Full Explanation
A single Azure storage account can provide endpoints for multiple data services—commonly blobs, files, queues, and tables—under one account namespace and shared settings. Separate subscriptions are not required per service simply to use more than one storage service. Fundamentals questions test that the account is a multi-service host rather than a single-service-only construct.