A colleague argues that because your resource group was created in West Europe, every resource inside it must also run in West Europe. Is that right?
Microsoft Certified: Azure Fundamentals (AZ-900), objective architecture-and-services. Azure architecture and services medium
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
The options
Correct No — a resource group can hold resources from several regions, and its own location only determines where the group's metadata is stored
Correct. Region is chosen per resource. The group's location matters for where its metadata lives, which is why an outage in that region can stop you updating the group even while the resources themselves are healthy elsewhere.
Not correct Yes — resources inherit the group's region and cannot be created outside it
Wrong. Nothing enforces that. Teams often do keep a group's resources in one region to avoid cross-region latency and egress charges, but that is a convention they chose, not a rule Azure applies.
Not correct No, and the group's location is meaningless metadata you can ignore
Wrong in its second half. The location is where the group's own metadata is stored, so it is not decorative — it is simply not a constraint on the resources inside.
Not correct Yes, unless an Azure Policy assignment explicitly permits other regions
Wrong, and it reverses the default. There is no built-in restriction to lift; a policy is how you opt in to restricting locations, not how you escape a restriction that was already there.
Why
Two independent facts get muddled here. A resource group is a management container whose members can sit in different regions, and the group's location is metadata, not gravity. If you want everything in a group pinned to one region, that is a rule you impose with Azure Policy — and there are good latency and cost reasons to want it — but it is your rule rather than the platform's.
Where this comes from
- Cited
- Microsoft AZ-900 study guide skill area architecture-and-services.core-architectural-components
Practise this
Reading one question is not practice. The trainer will draw a set from objective architecture-and-services and space the ones you get wrong.
Practise Microsoft Certified: Azure Fundamentals (AZ-900)
More questions on this objective
- An image-resizing routine runs for about two seconds whenever a file lands in a storage container — perhaps two hundred times on a busy day, and not at all on a quiet one. The team wants to pay for the work done and maintain no servers. Which compute option fits? machine-checked
- A fifteen-year-old accounting application needs a kernel-level driver, a scheduled task that edits the registry, and a runtime version nobody supports any more. The business wants it running in Azure this quarter with as few code changes as possible. Where does it go? machine-checked
- A team runs nine small services, each with its own conflicting library versions. They want each one packaged with its dependencies, starting in seconds, several to a host, without a separate operating system per service. Which compute type are they describing? machine-checked
- Which TWO of these statements about Azure compute types are true? machine-checked
- A public website runs on four identical virtual machines behind a load balancer. Traffic triples while a television advert airs and falls back an hour later. The team wants instances added and removed automatically against CPU, all built from one image, with nobody clicking. Which option is designed for that? machine-checked
- Three virtual machines form a quorum-based cluster in a region that has no availability zones. You want them placed so that neither a single rack losing power nor a single batch of planned host maintenance can take all three at once. What do you configure? machine-checked