A village CIO asks what an Azure storage account is in fundamentals terms. Which description is accurate?
Select an answer to reveal the explanation.
Short Explanation
Picture the storage account as the front door and address book for Azure Storage—blobs, files, queues, and tables live under that roof. It is not a lonely VHD, not Entra Domain Services DNS, and not an App Service plan. One account, multiple storage services underneath.
Full Explanation
An Azure storage account, in fundamentals terms, is a top-level namespace that can host Blob, File, Queue, and Table storage services under one account with shared endpoints and configuration. For a village CIO, that means the storage account is the front door and address book for Azure Storage data services rather than a single file or an unrelated compute SKU. Understanding the account as that multi-service container is core AZ-900 vocabulary.
A single unmanaged VHD file that replaces all Azure networking confuses classic disk artifacts with the storage-account resource and invents a networking replacement role it does not have. Only a DNS alias for Microsoft Entra Domain Services misstates both identity/domain services and storage—storage accounts are not Entra Domain Services DNS aliases. A compulsory App Service plan SKU for every municipality confuses web-app hosting plans with Azure Storage namespaces.
Exam caveat: not every account kind exposes every service or performance feature the same way; describe-level answers still start from the multi-service namespace idea before SKU deep dives. Operational check: create or open a municipal storage account in the portal, note the blob/file/queue/table endpoints under that account name, and show the CIO that multiple services can share one namespace.