High availability design patterns in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Load Balancer resource.

Azure

resource "azurerm_lb" "example" {
  name                = "example-lb"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  sku                 = "[1]"
}

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

AStandard

BBasic

CPremium

DFree

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Basic SKU which lacks zone redundancy.

Using Premium SKU which is not valid for Load Balancer.

Selecting Free which does not exist.

The Standard SKU is recommended for high availability because it supports zone redundancy and better performance.

2fill in blank

medium

Complete the code to define an availability set with fault domains.

Azure

resource "azurerm_availability_set" "example" {
  name                         = "example-avset"
  location                     = azurerm_resource_group.example.location
  resource_group_name          = azurerm_resource_group.example.name
  platform_fault_domain_count  = [1]
  platform_update_domain_count = 5
}

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

A3

B2

C1

D4

Attempts:

3 left

💡 Hint

Common Mistakes

Using 1 fault domain which offers no redundancy.

Using 4 which is not supported in some regions.

Confusing fault domains with update domains.

Setting platform_fault_domain_count to 3 distributes VMs across three fault domains for high availability.

3fill in blank

hard

Fix the error in the Azure Traffic Manager profile configuration.

Azure

resource "azurerm_traffic_manager_profile" "example" {
  name                = "example-tm"
  resource_group_name = azurerm_resource_group.example.name
  location            = "global"
  profile_status      = "Enabled"
  traffic_routing_method = "[1]"
  dns_config {
    relative_name = "exampletm"
    ttl           = 30
  }
}

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

ARoundRobin

BWeighted

CPerformance

DPriority

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect casing like 'weighted'.

Using unsupported routing methods.

Confusing routing method with profile status.

The correct traffic routing method is Weighted (case-sensitive) to distribute traffic evenly.

4fill in blank

hard

Fill both blanks to configure a virtual machine scale set with automatic upgrade policy.

Azure

resource "azurerm_linux_virtual_machine_scale_set" "example" {
  name                = "example-vmss"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name

  upgrade_policy_mode = "[1]"

  automatic_os_upgrade_policy {
    enable_auto_os_upgrade = [2]
  }
}

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

AManual

BAutomatic

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Manual' disables automatic upgrades.

Setting enable_auto_os_upgrade to false disables upgrades.

Using uppercase True or False causes errors.

Setting upgrade_policy_mode to Automatic enables automatic upgrades, and enable_auto_os_upgrade must be true to activate it.

5fill in blank

hard

Fill all three blanks to define a health probe and backend pool for an Azure Application Gateway.

Azure

resource "azurerm_application_gateway" "example" {
  name                = "example-appgw"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name

  backend_address_pool {
    name = "[1]"
  }

  probe {
    name                = "[2]"
    protocol            = "[3]"
    host                = "localhost"
    path                = "/health"
    interval            = 30
    timeout             = 30
    unhealthy_threshold = 3
  }
}

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

AbackendPool1

BhealthProbe1

CHttp

DHttps

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent names between backend pool and probe.

Setting protocol to 'Https' without proper certificates.

Leaving probe name empty.

The backend pool is named backendPool1, the probe is named healthProbe1, and the protocol is Http for health checks.