A county warehouse project learns that Azure storage accounts offer performance and account-kind choices. Which statement stays at describe-level accuracy?
Select an answer to reveal the explanation.
Short Explanation
Not all storage accounts are clones—Azure offers kind and performance flavors, including familiar standard versus premium themes. Fundamentals stops at knowing those choices exist, not memorizing every SKU footnote. Region still matters; premium is not “one container name.”
Full Explanation
At describe-level accuracy, storage accounts include type and performance options such as standard versus premium themes that affect supported features and workload fit. A county warehouse project should expect to choose account characteristics when creating storage rather than assuming every account is identical. AZ-900 expects awareness that these options exist without requiring memorization of every SKU cell.
Every storage account is identical with no performance or kind choices is false—creation flows expose meaningful type and performance decisions. Account kind is chosen only after deleting the Azure region list invents a nonsense prerequisite; region selection remains a first-class choice and is not removed by picking an account kind. Premium always means the account must run inside a single container name confuses performance tier themes with container naming; premium is not defined as “one container only.”
Exam caveat: premium versus standard choices can limit which services or access patterns are appropriate, so counties should match account options to the warehouse workload before bulk migration. Operational check: walk through storage-account creation for a pilot warehouse container, record the performance/account-kind selections in the project runbook, and confirm they align with expected Blob throughput and feature needs.