Question

Difficulty: HardAzure Resources, Resource Groups, Subscriptions, and Management Groups

An organization is restructuring its Azure environment to comply with new corporate policies. The current resource hierarchy and setup are as follows:
- A parent management group named Corp-MG contains two subscriptions: Sub-Production and Sub-Testing.
- Sub-Production contains a resource group named RG-App located in the West US region.
- RG-App contains a virtual machine named VM-Web deployed in the East US region.

An administrator is tasked with planning the following three actions:
1. Apply a tag to the resource group RG-App and have it automatically apply to VM-Web for billing categorization.
2. Move the virtual machine VM-Web from RG-App in Sub-Production to a new resource group in Sub-Testing while keeping the virtual machine running in the East US region.
3. Create a new resource group named RG-Database inside the existing RG-App resource group to group database resources.

Which of the administrative actions are supported in Azure?

  1. A
    Only action 1 and action 2 are supported.
  2. Only action 2 is supported.Answer
  3. C
    Only action 2 and action 3 are supported.
  4. D
    None of the actions are supported because a virtual machine must be redeployed to the region of the target subscription when moved.

Answer

Only action 2 is supported.
The option stating that only action 2 is supported is correct. Azure allows moving resources across resource groups and subscriptions, and their physical deployment region remains unchanged. In contrast, tags applied to a resource group are not inherited by resources, and resource groups cannot be nested in Azure.

Step-by-Step Solution

1
Evaluate Action 1 (Tag inheritance from Resource Group to Resource).
Action 1 is not supported.
Azure resources do not automatically inherit tags applied to their parent resource group. Tags must be applied directly to resources or enforced via Azure Policy.
2
Evaluate Action 2 (Moving a resource between resource groups/subscriptions and location independence).
Action 2 is supported.
Azure supports moving resources (like virtual machines) between resource groups and subscriptions. During the move, the resource's physical location (East US) does not change, and it does not need to match the resource group's location (West US).
3
Evaluate Action 3 (Nesting resource groups).
Action 3 is not supported.
Azure resource groups represent a flat organizational boundary and cannot be nested inside other resource groups.
4
Combine results to identify the correct option.
Only Action 2 is supported.
Based on the individual evaluations of the three actions, only the second action is supported by Azure.

Key Concept

Azure resource hierarchy, resource movement boundaries, resource group nesting limitations, and tag inheritance rules.
Rate this question