AZ-104 · Question #347
AZ-104 Question #347: Real Exam Question with Answer & Explanation
Azure App Service resources can be moved to other resource groups or subscriptions, but cannot be moved into a resource group that already contains App Service resources located in a different Azure region.
Question
Hotspot Question You have Azure subscriptions named Subscription1 and Subscription2. Subscription1 has following resource groups: RG1 includes a web app named App1 in the West Europe location. Subscription2 contains the following resource groups: For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point. Answer:
Options
- __typehotspot
- variantyes_no
Explanation
Azure App Service resources can be moved to other resource groups or subscriptions, but cannot be moved into a resource group that already contains App Service resources located in a different Azure region.
Approach. Based on the standard certification scenario this question is drawn from, the complete context is: Subscription1 contains RG1 (West Europe, contains App1) and RG2 (North Europe, contains App2). Subscription2 contains RG3 (West Europe, empty) and RG4 (North Europe, empty).
- App1 can be moved to RG2 (No): When moving an App Service within the same subscription, the destination resource group must not contain any existing App Service resources located in a different region. Since RG2 contains an App Service (App2) in North Europe, App1 (West Europe) cannot be moved there.
- App1 can be moved to RG3 (Yes): When moving across subscriptions, the destination resource group must not contain ANY existing App Service resources. Since RG3 is empty, the move is fully supported.
- App1 can be moved to RG4 (Yes): RG4 is also empty. A resource group's location (North Europe) only dictates where the group's metadata is stored, not where its resources must be located. Since RG4 has no conflicting App Service resources, moving a West Europe app into it is allowed.
Common mistakes.
- common_mistake. A frequent misconception is that a resource must reside in a Resource Group that shares its exact Azure region. Resource Group locations strictly define metadata storage; you can place a West Europe resource in a North Europe Resource Group. The only reason RG2 fails is due to a specific App Service architectural limitation regarding mixed-region App Service resources in the same group.
Concept tested. Azure App Service move limitations and Resource Group metadata properties across same-subscription and cross-subscription moves.
Topics
Community Discussion
No community discussion yet for this question.