Azure architecture

Management groups provide a level of scope above subscriptions, allowing organizations to manage access, policy, and compliance across multiple subscriptions efficiently. They do not sit below subscriptions or inside resource groups, which are lower-level containers used for grouping individual resources.

An Availability Zone consists of one or more physically separate datacenters within a region, equipped with independent power, cooling, and networking to ensure fault tolerance. It is not a subscription, which is a logical billing and management boundary rather than a physical location.

An Azure Resource Group is used to group, deploy, and manage related resources for a single solution, making it easier to manage and organize Azure resources. A diagram for this topic isn't available yet — the worked example below walks the same reasoning step by step.

• !Some people may confuse Azure Resource Groups with Azure Regions, which are physical locations where Azure datacenters are located, or with specific virtual machine sizes, which are used to define the size of a virtual machine.
• !Some people may confuse Azure Region pairs with other Azure features that provide faster CPUs or lower pricing, but Region pairs are specifically designed for replication and disaster recovery purposes.
• !They do not alter VM hardware performance to provide faster CPUs (Option A), nor do they inherently guarantee free egress.
• !They do not sit below subscriptions or inside resource groups, which are lower-level containers used for grouping individual resources.

Answer each from memory — you'll see instantly whether you're right and why.

Run a focused 10-question mini-mock on Azure architecture and see it stick.