Exam AZ-104 topic 2 question 24 discussion

Correct Answer: A You can only move a resource to a Resource Group or Subscription, but the location stays the same. When you move WebApp1 to RG2, the resource will be restricted based on the policy of the new Resource Group (Policy2).

A is correct

Tested in my Lab. A is correct

A is corerct

My understanding is that App service plans cannot move regions. If you wanted to move it you would have to recreate it in a new region. And since the policies in this case are applied at the resource group level, and the only thing moving is the outsource webapp1, not the resource group itself, then the policies of the new RG2 will apply.

Esta correta

Moving to a resource group in a different region doesn't also move the resources to the same region as the RG.. come on guys! RG just hold meta data of the connected resources

App Service resources are region-specific and can't be moved across regions. You must create a copy of your existing App Service resources in the target region, then move your content over to the new app. If your source app uses a custom domain, you can migrate it to the new app in the target region when you're finished. To make copying your app easier, you can clone an individual App Service app into an App Service plan in another region, but it does have limitations, especially that it doesn't support Linux apps.

https://www.youtube.com/watch?v=QBAOl2dZS_c Answer is B

I know its not the popular opinion but I think its correct. I got receipts... Everyone seems to get that when you move a resource to a new resource group you dont change its location, but knowing that why do you think it changes its app service plan? App Service plan lays out the region resources for the apps that run in it and the you just agreed the region of the actual app service is not changing. So why would it then change to a app service plan that's laying out region specific limits. Also according to MS... "You can move an app to another App Service plan, as long as the source plan and the target plan are in the same resource group, geographical region, and of the same OS type." According to this its not even possible to move the app to a new app service plan that's not in the same region or the same resource group... and why would it. Since the app service plan lays out the resources in a region that all of its apps will share? https://learn.microsoft.com/en-us/azure/app-service/app-service-plan-manage

Remember... "The resource group stores metadata about the resources. Therefore, when you specify a location for the resource group, you are specifying where that metadata is stored." This should help people understand why moving a resource into a new resource group will not change its location.

Respurce and RG can be in different regions. Moving a resource do different RG doesn;t change the resource's region.

"you cannot change an App Service plan's region. If you want to run your app in a different region" https://learn.microsoft.com/en-us/azure/app-service/app-service-plan-manage#move-an-app-to-a-different-region https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-limitations/app-service-move-limitations#move-across-subscriptions

Came in test yesterday

Answer A is correct. Verified and found that we can only change(Move) the RG2 of WebApp1. All other associated resources will be in same reason and same RG1. The activity is independent of app service plan. Even after moving the WebApp1 to RG2 the WebApp1 location will be West Europe only.

I tried this in a lab today, and the answer is C. The Policy 1 was carried along when I moved the web app from RG1 to RG2. I kept a simple policy to append tag and its default (policy1: name: RGroup ; value RG1; policy2: RGroup RG2). and the same tag remained as is when the web app was moved RG2

It never says it moves region. It just moves RG. There are some limitations in moving some resources. In case of webapps, it shouldn’t have any issue.