Describe Azure architecture and services practice questions

A resource group is a logical container for related resources.

A resource group logically groups related resources so you can manage them as one unit; it is not a billing boundary (that is the subscription), not a physical datacenter, and not a container of subscriptions (that is a management group).

1. Recall the definition of a resource group as a logical container.
2. Separate it from the subscription (billing) and management group (subscription organization).
3. Note that a resource group is logical, not a physical datacenter.

Exam tip: A resource group is a logical container for related resources, nothing more.

The subscription is the billing and access boundary.

The subscription receives the bill and is the boundary for assigning access and enforcing limits, and it contains resource groups. A resource group only organizes resources, a management group organizes subscriptions, and a resource is a single service instance.

1. Identify the described role: billing and access boundary holding resource groups.
2. Match it to the subscription.
3. Distinguish it from resource groups, management groups, and individual resources.

Exam tip: The subscription is the billing and access boundary in Azure.

Management groups organize and manage multiple subscriptions together.

A management group is a container above subscriptions; settings applied to it flow down to every subscription inside, which matches the requirement. Resource groups work only inside one subscription, while region pairs and availability zones are physical resilience concepts.

1. Note the requirement: manage many subscriptions together with inheritance.
2. Recall that management groups sit above subscriptions and pass settings down.
3. Eliminate resource groups and the physical resilience concepts.

Exam tip: Managing multiple subscriptions together points to management groups.

The Azure hierarchy runs management group, subscription, resource group, resource.

Reading top to bottom, a management group contains subscriptions, each subscription contains resource groups, and each resource group contains resources. The other orders either reverse the chain or swap adjacent levels, breaking the containment relationship.

1. Start at the top with the broadest container, the management group.
2. Descend through subscription, then resource group, then resource.
3. Confirm each level contains the one below it.

Exam tip: Memorize: management group, subscription, resource group, resource.

Azure Resource Manager is the single management layer for all requests.

Every management request, no matter which tool sends it, goes through Azure Resource Manager, which checks permissions and carries it out consistently. Subscriptions, regions, and resource groups are boundaries and containers, not the processing layer.

1. Identify the described role: the single layer every request passes through.
2. Match it to Azure Resource Manager (ARM).
3. Distinguish ARM from boundaries and containers.

Exam tip: Azure Resource Manager is the front door for all resource management.

A region is a group of nearby datacenters connected by a low-latency network.

A region is a defined geographic area containing one or more networked datacenters, which is where you deploy resources. It is not a single rack, not a billing boundary (that is a subscription), and not a resource container (that is a resource group).

1. Recall the definition of a region as networked datacenters in an area.
2. Separate the physical region from logical constructs like subscriptions and resource groups.
3. Confirm the region is the where of a deployment.

Exam tip: A region is a set of nearby, networked datacenters where your resources run.