A records officer is creating an Azure storage account for resident privacy-sensitive scans. Why do naming and region choices matter at a describe level?
Select an answer to reveal the explanation.
Short Explanation
Where you plant the account (region) is where the data primarily lives, and the account name shows up in those *.core.windows.net style endpoints. Privacy-minded cities care about residency; ops cares that the name is unique and URL-friendly. It is not a desktop-only or PowerPoint-only decision.
Full Explanation
Creating a storage account requires selecting an Azure region, which affects where primary data resides and can matter for compliance and latency. The globally unique account name becomes part of the service endpoint URLs used to reach blobs and other services. AZ-900 describe-level items expect candidates to recognize that region and naming are meaningful configuration choices, not cosmetic or irrelevant details.