-
Hi Jessie and AS,
Thank you for sharing your feedback.
Resources of the resource group can be located in different regions than its associated resource group. A resource group stores metadata about the resources in a specific region where it was created, but the actual Azure resources that it contains can be in a totally different region. When you specify a location for the resource group, you’re practically specifying where that metadata is stored.
The actual scenario is a hotspot question containing 3 items, as shown below:
– Resource groups cannot span multiple regions = No
– Resources can connect to other resources located in another resource group = Yes
– You can add or remove a resource to a resource group at any time = Yes
The word “span” basically means the coverage or the scope of something. This term is used in AWS and the documentation of other cloud service providers when describing the reach of a particular service/resource, so the word itself shouldn’t be the issue.
The first statement says: “Resource groups cannot span multiple regions”
I understand that it may seem a little ambiguous at first, but that statement doesn’t mention anything about its “resources”, which is what you’ll see in the second statement. Therefore, this one is clearly alluding to the actual resource itself. Nonetheless, I do get the confusion that this statement brings.
To avoid any issues, we have just revised this scenario to further accentuate that we are talking about the resource group itself and not its resources.
Let us know if you need further assistance. The Tutorials Dojo team is dedicated to help you pass your AWS exam on your first try!
Regards,
Jon Bonso @ Tutorials Dojo
