Multi-region deployment patterns in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the primary region for deployment.

Azure

resourceGroup = new ResourceGroup('myResourceGroup', { location: '[1]' });

Drag options to blanks, or click blank then click option'

Awestus2

Bcentralus

Ceastus

Dnorthcentralus

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid region name.

Leaving the location blank.

The primary region is set to westus2 to deploy resources in that Azure region.

2fill in blank

medium

Complete the code to create a secondary region resource group for disaster recovery.

Azure

secondaryResourceGroup = new ResourceGroup('mySecondaryRG', { location: '[1]' });

Drag options to blanks, or click blank then click option'

Aeastus2

Bwestus2

Csouthcentralus

Deastus

Attempts:

3 left

💡 Hint

Common Mistakes

Using the same region as the primary resource group.

Choosing a region too far causing latency issues.

The secondary resource group is created in eastus2 to enable multi-region redundancy.

3fill in blank

hard

Fix the error in the code to enable geo-replication for the storage account.

Azure

storageAccount = new StorageAccount('mystorage', { location: 'westus2', sku: { name: '[1]' } });

Drag options to blanks, or click blank then click option'

APremium_LRS

BStandard_GRS

CStandard_LRS

DStandard_ZRS

Attempts:

3 left

💡 Hint

Common Mistakes

Using LRS which is locally redundant only.

Choosing Premium SKU which may not support geo-replication.

Using Standard_GRS enables geo-redundant storage for multi-region replication.

4fill in blank

hard

Fill both blanks to configure traffic manager profile with priority routing and specify the primary endpoint.

Azure

const profile = new TrafficManagerProfile('tmProfile', {
  routingMethod: '[1]',
  endpoints: [{
    name: 'primaryEndpoint',
    type: 'azureEndpoints',
    targetResourceId: '[2]'
  }]
});

Drag options to blanks, or click blank then click option'

APriority

BWeighted

C/subscriptions/123/resourceGroups/myResourceGroup/providers/Microsoft.Network/publicIPAddresses/primaryIP

D/subscriptions/123/resourceGroups/myResourceGroup/providers/Microsoft.Network/publicIPAddresses/secondaryIP

Attempts:

3 left

💡 Hint

Common Mistakes

Using Weighted routing when Priority is required.

Specifying the secondary endpoint as primary.

The routing method Priority directs traffic to the primary endpoint specified by the resource ID primaryIP.

5fill in blank

hard

Fill all three blanks to define an Azure Front Door with two backend pools for multi-region failover.

Azure

const frontDoor = new FrontDoor('myFrontDoor', {
  backendPools: [
    {
      name: '[1]',
      backends: [{ address: '[2]' }]
    },
    {
      name: '[3]',
      backends: [{ address: 'secondary.example.com' }]
    }
  ]
});

Drag options to blanks, or click blank then click option'

AprimaryPool

Bprimary.example.com

CsecondaryPool

DfailoverPool

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up pool names and addresses.

Using the same name for both pools.

The backend pools are named primaryPool and secondaryPool with addresses primary.example.com and secondary.example.com respectively for failover.

Practice

1. What is the main benefit of deploying an application in multiple Azure regions?

easy

A. Improves application speed and availability worldwide

B. Reduces the cost of Azure services

C. Simplifies the application code

D. Limits the number of users who can access the app

Solution

1. Step 1: Understand multi-region deployment purpose

   Deploying in multiple regions helps serve users faster by placing resources closer to them.

2. Step 2: Identify the key benefit

   This setup also increases availability by providing backups if one region fails.

3. Final Answer:

   Improves application speed and availability worldwide -> Option A

4. Quick Check:

   Multi-region deployment = better speed and availability [OK]

Hint: Think about user experience worldwide for multi-region [OK]

Common Mistakes:

• Confusing cost reduction with performance improvement
• Assuming code changes are needed for multi-region
• Believing multi-region limits users

2. Which Azure service is used to route users automatically to the best performing region?

easy

A. Azure Traffic Manager

B. Azure Blob Storage

C. Azure Virtual Network

D. Azure Functions

Solution

1. Step 1: Identify routing service for multi-region

   Azure Traffic Manager directs user requests to the fastest or healthiest region.

2. Step 2: Exclude unrelated services

   Blob Storage stores data, Virtual Network manages networking, Functions run code; none route traffic.

3. Final Answer:

   Azure Traffic Manager -> Option A

4. Quick Check:

   Traffic Manager routes users to best region [OK]

Hint: Traffic Manager controls user routing in multi-region setups [OK]

Common Mistakes:

• Choosing storage or compute services instead of routing
• Confusing Virtual Network with Traffic Manager
• Assuming Functions handle traffic routing

3. Given this Azure Traffic Manager profile configuration snippet:

{
  "name": "myTrafficManager",
  "type": "Microsoft.Network/trafficManagerProfiles",
  "properties": {
    "trafficRoutingMethod": "Performance",
    "endpoints": [
      {"name": "eastUS", "type": "Microsoft.Network/trafficManagerProfiles/azureEndpoints", "properties": {"targetResourceId": "/subscriptions/.../eastUSApp"}},
      {"name": "westEurope", "type": "Microsoft.Network/trafficManagerProfiles/azureEndpoints", "properties": {"targetResourceId": "/subscriptions/.../westEuropeApp"}}
    ]
  }
}

What does the Performance routing method do?

medium

A. Routes users to the endpoint with the highest CPU usage

B. Routes users randomly to any endpoint

C. Routes users to the endpoint with the oldest deployment

D. Routes users to the endpoint with the lowest network latency

Solution

1. Step 1: Understand Performance routing method

   Performance routing sends users to the endpoint with the lowest network latency for faster response.

2. Step 2: Eliminate incorrect options

   Random routing is 'Weighted' or 'Priority', CPU usage and deployment age are not routing criteria.

3. Final Answer:

   Routes users to the endpoint with the lowest network latency -> Option D

4. Quick Check:

   Performance routing = lowest latency endpoint [OK]

Hint: Performance routing means fastest response endpoint [OK]

Common Mistakes:

• Confusing Performance with random or priority routing
• Thinking CPU usage affects routing
• Assuming deployment age affects routing

4. You deployed your app in two Azure regions but users report slow failover when one region goes down. What is the most likely cause?

medium

A. You used Performance routing with health probes enabled

B. Azure Traffic Manager is set to Priority routing but no health probes are configured

C. You deployed the app only in one region

D. Azure Traffic Manager is disabled

Solution

1. Step 1: Analyze failover issue with Priority routing

   Priority routing requires health probes to detect endpoint health and failover quickly.

2. Step 2: Identify missing health probes impact

   Without health probes, Traffic Manager cannot detect failure and delays failover.

3. Final Answer:

   Azure Traffic Manager is set to Priority routing but no health probes are configured -> Option B

4. Quick Check:

   Priority routing needs health probes for fast failover [OK]

Hint: Priority routing needs health probes to detect failures [OK]

Common Mistakes:

• Assuming Performance routing causes slow failover
• Thinking single-region deployment causes failover delay
• Ignoring health probe configuration

5. You want to deploy a global web app with low latency and high availability. Which multi-region deployment pattern should you choose in Azure to achieve this?

hard

A. Deploy app in one region and rely on Azure Virtual Network peering

B. Deploy app in one region and use Azure CDN only

C. Deploy app instances in multiple regions and use Azure Traffic Manager with Performance routing

D. Deploy app in multiple regions but disable Traffic Manager

Solution

1. Step 1: Identify deployment for low latency and high availability

   Deploying app instances in multiple regions places resources closer to users and provides redundancy.

2. Step 2: Use Azure Traffic Manager with Performance routing

   This routes users to the fastest region automatically, improving speed and availability.

3. Step 3: Exclude less effective options

   Single region with CDN or VNet peering does not provide true multi-region failover or latency benefits; disabling Traffic Manager prevents routing.

4. Final Answer:

   Deploy app instances in multiple regions and use Azure Traffic Manager with Performance routing -> Option C

5. Quick Check:

   Multi-region + Traffic Manager Performance = best global deployment [OK]

Hint: Combine multi-region deployment with Traffic Manager Performance routing [OK]

Common Mistakes:

• Relying on CDN alone for global app availability
• Disabling Traffic Manager in multi-region setup
• Using single region for global low latency