Why DNS management matters in AWS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Route 53 hosted zone with the correct domain name.

AWS

resource "aws_route53_zone" "primary" {
  name = "[1]"
}

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

Avpc-123abc

Bmybucket

Cus-east-1

Dexample.com

Attempts:

3 left

💡 Hint

Common Mistakes

Using a bucket name instead of a domain name.

Using a region or VPC ID instead of a domain name.

The name field must be the domain name you want to manage in Route 53, like example.com.

2fill in blank

medium

Complete the code to create an A record pointing to an IP address in Route 53.

AWS

resource "aws_route53_record" "web" {
  zone_id = aws_route53_zone.primary.zone_id
  name    = "www"
  type    = "A"
  ttl     = 300
  records = ["[1]"]
}

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

Avpc-123abc

Bexample.com

C192.0.2.44

Dus-east-1

Attempts:

3 left

💡 Hint

Common Mistakes

Using a domain name instead of an IP address for an A record.

Using AWS resource IDs or region names instead of IP addresses.

The records field for an A record must be an IP address, like 192.0.2.44.

3fill in blank

hard

Fix the error in the code by selecting the correct record type for a domain alias to an S3 website endpoint.

AWS

resource "aws_route53_record" "alias" {
  zone_id = aws_route53_zone.primary.zone_id
  name    = "static"
  type    = "[1]"
  alias {
    name                   = aws_s3_bucket.website.website_endpoint
    zone_id                = aws_s3_bucket.website.hosted_zone_id
    evaluate_target_health = false
  }
}

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

AA

BCNAME

CTXT

DMX

Attempts:

3 left

💡 Hint

Common Mistakes

Using CNAME for alias records to AWS resources.

Using TXT or MX record types incorrectly.

Alias records to AWS resources like S3 website endpoints must use type A in Route 53.

4fill in blank

hard

Fill both blanks to create a health check that monitors an HTTP endpoint on port 80.

AWS

resource "aws_route53_health_check" "web_health" {
  type                = "[1]"
  resource_path       = "/"
  failure_threshold   = 3
  port                = [2]
  request_interval    = 30
  ip_address          = "192.0.2.44"
}

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

AHTTP

B80

CHTTPS

D443

Attempts:

3 left

💡 Hint

Common Mistakes

Using HTTPS type with port 80.

Using HTTP type with port 443.

The health check type for HTTP is HTTP and the port for HTTP is 80.

5fill in blank

hard

Fill all three blanks to create a Route 53 record that routes traffic to an Elastic Load Balancer.

AWS

resource "aws_route53_record" "elb_alias" {
  zone_id = aws_route53_zone.primary.zone_id
  name    = "app"
  type    = "[1]"
  alias {
    name                   = aws_lb.app.dns_name
    zone_id                = aws_lb.app.zone_id
    evaluate_target_health = [2]
  }
  ttl     = [3]
}

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

AA

Btrue

C300

DCNAME

Attempts:

3 left

💡 Hint

Common Mistakes

Using CNAME type for ELB alias records.

Setting evaluate_target_health to false when health checks are needed.

Using very high or zero TTL values.

Alias records to ELB use type A. The evaluate_target_health is usually set to true to check ELB health. TTL is commonly set to 300 seconds.