Route 53 with ELB integration in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Route 53 record that points to an ELB.

AWS

resource "aws_route53_record" "example" {
  zone_id = aws_route53_zone.example.zone_id
  name    = "www.example.com"
  type    = "[1]"
  alias {
    name                   = aws_lb.example.dns_name
    zone_id                = aws_lb.example.zone_id
    evaluate_target_health = true
  }
}

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

AMX

BA

CTXT

DCNAME

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'CNAME' record type instead of 'A' for ELB alias

Using unsupported record types like 'TXT' or 'MX'

When pointing a Route 53 record to an ELB using an alias, the record type must be A.

2fill in blank

medium

Complete the code to enable health check evaluation for the alias record.

AWS

resource "aws_route53_record" "example" {
  zone_id = aws_route53_zone.example.zone_id
  name    = "app.example.com"
  type    = "A"
  alias {
    name                   = aws_lb.app.dns_name
    zone_id                = aws_lb.app.zone_id
    evaluate_target_health = [1]
  }
}

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

A"false"

Bfalse

C"true"

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using quoted strings "true" or "false" instead of boolean true or false

Setting evaluate_target_health to false disables health checks

The evaluate_target_health attribute must be set to the boolean true (without quotes) to enable health check evaluation.

3fill in blank

hard

Fix the error in the Route 53 record type for alias to ELB.

AWS

resource "aws_route53_record" "fix" {
  zone_id = aws_route53_zone.fix.zone_id
  name    = "service.example.com"
  type    = "[1]"
  alias {
    name                   = aws_lb.service.dns_name
    zone_id                = aws_lb.service.zone_id
    evaluate_target_health = true
  }
}

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

ATXT

BCNAME

CA

DNS

Attempts:

3 left

💡 Hint

Common Mistakes

Using CNAME instead of A for alias records to ELB

Using unsupported record types like TXT or NS

When creating an alias record to an ELB, the record type should be A, not CNAME. Alias records use type A for ELB targets.

4fill in blank

hard

Fill both blanks to create a Route 53 alias record pointing to an ELB with health check evaluation.

AWS

resource "aws_route53_record" "multi" {
  zone_id = aws_route53_zone.multi.zone_id
  name    = "api.example.com"
  type    = "[1]"
  alias {
    name                   = aws_lb.api.dns_name
    zone_id                = aws_lb.api.zone_id
    evaluate_target_health = [2]
  }
}

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

AA

Btrue

Cfalse

DCNAME

Attempts:

3 left

💡 Hint

Common Mistakes

Using CNAME as record type for alias

Setting evaluate_target_health to false disables health checks

The record type for alias to ELB is A, and evaluate_target_health should be set to boolean true to enable health checks.

5fill in blank

hard

Fill all three blanks to create a Route 53 alias record with correct type, health check enabled, and zone ID from ELB.

AWS

resource "aws_route53_record" "full" {
  zone_id = aws_route53_zone.full.zone_id
  name    = "web.example.com"
  type    = "[1]"
  alias {
    name                   = aws_lb.web.dns_name
    zone_id                = [2]
    evaluate_target_health = [3]
  }
}

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

AA

Baws_lb.web.zone_id

Ctrue

DCNAME

Attempts:

3 left

💡 Hint

Common Mistakes

Using CNAME as record type

Not referencing ELB zone ID properly

Disabling health checks by setting evaluate_target_health to false

Alias record type must be A. The ELB's zone ID is referenced as aws_lb.web.zone_id. Health check evaluation is enabled by setting evaluate_target_health to true.