Routing policies (simple, weighted, latency) in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a simple routing policy in AWS Route 53.

AWS

resource "aws_route53_record" "simple_record" {
  zone_id = "Z123456789"
  name    = "example.com"
  type    = "A"
  ttl     = 300
  records = ["[1]"]
}

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

A192.0.2.44

Bexample.com

C300

DZ123456789

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the zone ID or TTL in the records field.

Using the domain name instead of an IP address.

The records field requires the IP address for the A record. Here, "192.0.2.44" is the correct IP address.

2fill in blank

medium

Complete the code to set a weighted routing policy with weight 100.

AWS

resource "aws_route53_record" "weighted_record" {
  zone_id = "Z987654321"
  name    = "app.example.com"
  type    = "A"
  ttl     = 60
  records = ["192.0.2.55"]
  set_identifier = "app1"
  [1] = 100
}

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

Aweight

Blatency

Cfailover

Dhealth_check_id

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'latency' instead of 'weight' for weighted routing.

Omitting the 'set_identifier' which is required for weighted records.

The weight attribute sets the traffic weight for weighted routing. Setting it to 100 directs more traffic to this record.

3fill in blank

hard

Fix the error in the latency routing policy by completing the missing attribute.

AWS

resource "aws_route53_record" "latency_record" {
  zone_id = "Z112233445"
  name    = "service.example.com"
  type    = "A"
  ttl     = 30
  records = ["192.0.2.66"]
  set_identifier = "us-east-1"
  [1] = "us-east-1"
}

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

Alatency_routing_policy

Bweight

Cregion

Dfailover

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'weight' instead of 'region' in latency routing.

Omitting the 'set_identifier' which is required.

The region attribute specifies the AWS region for latency routing policies.

4fill in blank

hard

Fill both blanks to configure a weighted routing policy with a health check.

AWS

resource "aws_route53_record" "weighted_health_check" {
  zone_id       = "Z556677889"
  name          = "api.example.com"
  type          = "A"
  ttl           = 60
  records       = ["192.0.2.77"]
  set_identifier = "api1"
  [1] = 200
  [2] = "hc-1234567890abcdef"
}

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

Aweight

Bhealth_check_id

Cregion

Dfailover

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'region' with 'weight' in weighted routing.

Omitting 'health_check_id' when health checks are needed.

The weight attribute sets the traffic weight, and health_check_id links the record to a health check for failover or weighted routing.

5fill in blank

hard

Fill all three blanks to create a latency routing policy with a health check and set identifier.

AWS

resource "aws_route53_record" "latency_health" {
  zone_id       = "Z998877665"
  name          = "web.example.com"
  type          = "A"
  ttl           = 20
  records       = ["192.0.2.88"]
  set_identifier = [1]
  [2] = "us-west-2"
  [3] = "hc-abcdef1234567890"
}

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

A"west-coast-server"

Bregion

Chealth_check_id

Dweight

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'weight' instead of 'region' for latency routing.

Not quoting the set_identifier string.

The set_identifier names the record, region specifies the AWS region for latency routing, and health_check_id links the health check.