Azure global infrastructure (regions, availability zones) - Step-by-Step Execution

Process Flow - Azure global infrastructure (regions, availability zones)

User request resource

↓

Select Azure Region

↓

Check Availability Zones

↓

Zone 1

↓

Deploy resources in zones

↓

Ensure high availability

↓

User accesses service

This flow shows how Azure chooses a region and availability zones to deploy resources for high availability and fault tolerance.

Execution Sample

Azure

Request VM in 'East US' region
Check zones in 'East US'
Deploy VM in Zone 1
Deploy VM in Zone 2
Deploy VM in Zone 3

This example shows deploying virtual machines across three availability zones in the East US region for fault tolerance.

Process Table

Step	Action	Region Selected	Zones Checked	Deployment Outcome
1	User requests VM	East US	N/A	Waiting for zone selection
2	Check zones in region	East US	Zone 1, Zone 2, Zone 3	Zones available
3	Deploy VM in Zone 1	East US	Zone 1	VM deployed in Zone 1
4	Deploy VM in Zone 2	East US	Zone 2	VM deployed in Zone 2
5	Deploy VM in Zone 3	East US	Zone 3	VM deployed in Zone 3
6	Ensure high availability	East US	Zones 1-3	VMs running in multiple zones
7	User accesses service	East US	Zones 1-3	Service available with zone redundancy

💡 All VMs deployed across zones in East US, ensuring high availability and fault tolerance.

Status Tracker

Variable	Start	After Step 2	After Step 5	Final
Region Selected	None	East US	East US	East US
Zones Checked	None	Zone 1, Zone 2, Zone 3	Zone 1, Zone 2, Zone 3	Zone 1, Zone 2, Zone 3
VMs Deployed	0	0	3	3
High Availability	False	False	True	True

Key Moments - 2 Insights

Why do we deploy VMs in multiple availability zones instead of just one?

Deploying VMs in multiple zones prevents service disruption if one zone fails, as shown in steps 3 to 6 where VMs are deployed in Zone 1, 2, and 3 to ensure high availability.

What happens if a region does not have availability zones?

If a region lacks availability zones, resources deploy in that region without zone redundancy, which means less fault tolerance. This is implied in step 2 where zones are checked before deployment.

Visual Quiz - 3 Questions

Look at the execution table, at which step are all three VMs deployed?

A Step 5

B Step 3

C Step 6

D Step 7

💡 Hint

Check the 'VMs Deployed' variable in variable_tracker after each step.

According to the variable_tracker, when does high availability become true?

A After Step 6

B After Step 5

C After Step 3

D After Step 2

💡 Hint

Look at the 'High Availability' row in variable_tracker.

If the region had only one availability zone, how would the deployment outcome change in the execution_table?

A VMs would deploy in multiple zones anyway

B Deployment would fail due to lack of zones

C VMs would deploy only in the single zone available

D User request would be redirected to another region automatically

💡 Hint

Refer to step 2 and 3 in execution_table about zones checked and deployment.

Concept Snapshot

Azure global infrastructure uses regions, which are geographic areas.
Each region can have multiple availability zones.
Availability zones are separate physical locations within a region.
Deploying resources across zones improves fault tolerance.
If one zone fails, others keep services running.
Always check zone availability before deployment.

Full Transcript

Azure global infrastructure consists of regions and availability zones. When a user requests a resource, Azure selects a region first. Then it checks which availability zones exist in that region. Availability zones are physically separate locations within the same region. Deploying resources like virtual machines across multiple zones ensures high availability and fault tolerance. If one zone has a problem, the other zones keep the service running. This process involves selecting the region, checking zones, deploying resources in each zone, and then providing the service to the user with redundancy. If a region has no availability zones, resources deploy without zone redundancy, which reduces fault tolerance.