Start with the type of boundary
Azure geography and resource administration answer different questions. A region groups Azure infrastructure in a geographic area; availability zones provide separated infrastructure locations within a supported region. Physical datacenters support that infrastructure. A resource group, subscription or management group instead organizes resource management. Do not assume that two resources in one resource group share a physical facility, or that moving a resource between administrative groupings provides a new failure boundary.
Read placement claims carefully
A requirement to keep data in a stated geographic area constrains placement. A requirement to reduce exposure to a zone-level disruption concerns failure isolation within services and regions that support the relevant zone design. Neither statement proves that an application automatically fails over, nor that every service has identical regional features. Region pairs and sovereign-region details require their own current service/region evidence; this lesson uses selected region/zone concepts rather than teaching all such arrangements. It does not quote a region count, latency or SLA percentage.
Worked example
A fictional heritage project has two administrative resource groups, Research and Publishing, inside one subscription. Its supplied placement note puts both groups’ workloads in the same region and states that both active copies of one service are in the same zone. First list management facts separately: group names and subscription ownership organize administration. Next list placement facts: the active copies share the stated zone. The fact that their resource groups differ does not change that placement. To evaluate a zone-resilience proposal, inspect the actual service deployment and supported placement, rather than treating the group names as physical separation.
Trace the administrative hierarchy
A resource is an individual managed entity. Resource groups collect related resources for management. Subscriptions form a broader administrative and billing context, and management groups can organize subscriptions under higher-level governance scope. This hierarchy is useful when deciding where a permission or governance assignment should apply. It does not mean that a subscription is a separate physical region. A narrow resource-group action and a subscription-wide action have different scopes even when the resources happen to share a region.
Transfer check
A fictional team creates a new subscription and concludes that a workload has therefore moved away from its previous region. No placement change is described. Is the conclusion supported? Check basis: no. The subscription changes administrative context; a geographic move requires separate placement evidence. Explain both the missing geographic fact and the management purpose the new subscription might serve. Use the independent region/zone guide to critique a different placement case, and retain all unassessed regional/service-specific details as coverage gaps.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
What are Azure regions?What are availability zones?Organize your Azure resources effectivelyWhat is Azure Resource Manager?