Examkin

Soru

Zorluk: OrtaAzure Resources, Resource Groups, Subscriptions, and Management Groups

A startup is deploying a web application that requires resources in both the East US and West Europe regions. The team needs to manage the lifecycle of these resources together as a single logical unit and track their costs using metadata tags. Which approach should the team use to organize and tag these resources?

  1. A
    Create a parent resource group in East US, nest a child resource group inside it for the West Europe resources, and apply tags only to the parent resource group.
  2. Deploy all resources to a single resource group, specifying the appropriate region (East US or West Europe) for each resource, and apply tags individually to both the resource group and each resource.Cevap
  3. C
    Create two separate resource groups, because Azure resources must reside in the same region as their containing resource group, and apply tags to both groups.
  4. D
    Deploy all resources to a single resource group, apply the required tags to that resource group, and rely on the containing resources to automatically inherit these tags.

Cevap

Deploying all resources to a single resource group across different regions and applying tags directly to both the resource group and the individual resources is the correct approach.
The correct approach is to place all resources in a single resource group and apply tags to individual resources. A resource group acts as a logical container that can hold resources deployed in different geographical regions. However, because resources do not automatically inherit tags from their resource group, tags must be applied to each resource individually to ensure accurate cost tracking.

Adım Adım Çözüm

1
Determine if resources in different regions can be grouped in the same resource group.
Yes, an Azure resource group can contain resources from different geographical regions.
A resource group is a logical container, and its location only dictates where the metadata is stored, not where the resources must reside.
2
Check if resource groups can be nested to manage regional resources.
No, Azure does not support nesting resource groups.
The resource hierarchy allows resource groups directly under subscriptions, but not inside other resource groups.
3
Determine if tags are inherited from a resource group to its resources.
No, resources do not inherit tags from the resource group.
Tags must be applied directly to resources or enforced via Azure Policy to appear on individual resources.
4
Select the option that correctly combines these rules.
The choice recommending a single resource group with individual resource tagging and regional flexibility is correct.
It matches all Azure resource group and tagging behaviors.

Anahtar Kavram

Azure Resource Group regional flexibility, nesting limits, and resource tag non-inheritance.
Bu soruyu puanla

Konular

Azure Resources, Resource Groups, Subscriptions, and Management Groups