Citizen data residency rules require that Azure resources for a city remain only in an approved list of regions. Which Azure Policy purpose best supports that geo-compliance goal?
Select an answer to reveal the explanation.
Short Explanation
If the city may only build in certain Azure regions, Policy is the gate that checks location. Tags do not teleport resources, and turning off subscriptions is not a residency strategy.
Full Explanation
Azure Policy commonly enforces allowed locations so resources can be created only in approved regions—supporting geo-compliance and data residency programs. Tags label resources but do not relocate them. Bastion and subscription disablement are not region-restriction mechanisms for this fundamentals scenario.