Azure Front Door overview - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Front Door resource with a global routing method.

Azure

resource "azurerm_frontdoor" "example" {
  name                = "example-frontdoor"
  resource_group_name = "example-rg"
  routing_method      = "[1]"
}

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

ALatency

BPriority

CWeighted

DRoundRobin

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a routing method not supported by Azure Front Door.

Using 'RoundRobin' which is not a valid routing method here.

The Latency routing method routes traffic to the backend with the lowest latency, which is common for Azure Front Door to optimize performance globally.

2fill in blank

medium

Complete the code to define a backend pool with health probes enabled.

Azure

backend_pool {
  name                = "backendPool1"
  load_balancing_name = "loadBalancingSettings1"
  health_probe_name   = "[1]"
}

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

AhealthProbeSettings1

BprobeSettings

ChealthCheck

Dprobe1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a name that does not match any health probe configuration.

Leaving the health_probe_name empty.

The healthProbeSettings1 is the correct name for the health probe configuration referenced in the backend pool.

3fill in blank

hard

Fix the error in the frontend endpoint configuration by completing the missing protocol.

Azure

frontend_endpoint {
  name                              = "frontendEndpoint1"
  host_name                         = "example.azurefd.net"
  session_affinity_enabled          = true
  session_affinity_ttl_seconds      = 60
  web_application_firewall_policy_link_id = null
  custom_https_configuration {
    certificate_source = "FrontDoor"
    protocol_type     = "[1]"
  }
}

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

AHttp

BHttpsOnly

CHttps

DHttpOnly

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Http' which is not secure.

Using invalid protocol names like 'HttpOnly' or 'HttpsOnly'.

The Https protocol_type enables secure HTTPS traffic for the frontend endpoint.

4fill in blank

hard

Fill both blanks to configure a routing rule that forwards traffic from the frontend to the backend pool.

Azure

routing_rule {
  name               = "routingRule1"
  frontend_endpoints = ["[1]"]
  accepted_protocols = ["[2]"]
  route_configuration {
    forwarding_configuration {
      backend_pool_name = "backendPool1"
    }
  }
}

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

AfrontendEndpoint1

BbackendPool1

CHttps

DHttp

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing backend pool name in frontend_endpoints.

Using 'Http' when HTTPS is required.

The frontendEndpoint1 is the correct frontend endpoint name, and Https is the accepted protocol for secure traffic.

5fill in blank

hard

Fill all three blanks to define a health probe with interval, path, and protocol settings.

Azure

health_probe_settings {
  name                = "healthProbeSettings1"
  interval_in_seconds  = [1]
  path                = "[2]"
  protocol            = "[3]"
}

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

A30

B/healthcheck

CHttps

DHttp

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTPS protocol for health probes when HTTP is expected.

Incorrect path or interval values.

The health probe checks every 30 seconds, uses the path /healthcheck, and the Http protocol for the probe.