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.