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.

Practice

1. What does a simple routing policy do in AWS Route 53?

easy

A. Sends all traffic to a single resource

B. Splits traffic based on weights

C. Routes traffic based on lowest latency

D. Routes traffic randomly among resources

Solution

1. Step 1: Understand simple routing purpose

   Simple routing sends all user requests to one resource without splitting or conditions.

2. Step 2: Compare with other routing types

   Weighted routing splits traffic, latency routing chooses fastest server, so they differ from simple routing.

3. Final Answer:

   Sends all traffic to a single resource -> Option A

4. Quick Check:

   Simple routing = single destination [OK]

Hint: Simple routing means one destination for all traffic [OK]

Common Mistakes:

• Confusing simple routing with weighted routing
• Thinking simple routing balances traffic
• Assuming simple routing uses latency

2. Which of the following is the correct way to configure a weighted routing policy in AWS Route 53?

easy

A. Assign weights to each record to split traffic

B. Set a single IP address for all traffic

C. Use latency measurements to route traffic

D. Randomly assign traffic without weights

Solution

1. Step 1: Identify weighted routing configuration

   Weighted routing requires assigning numeric weights to DNS records to control traffic distribution.

2. Step 2: Eliminate incorrect options

   Single IP is simple routing, latency routing uses latency, random without weights is invalid.

3. Final Answer:

   Assign weights to each record to split traffic -> Option A

4. Quick Check:

   Weighted routing = assign weights [OK]

Hint: Weighted routing needs numeric weights per record [OK]

Common Mistakes:

• Confusing weighted with simple routing
• Using latency instead of weights
• Not assigning any weight values

3. Given two servers in different regions with latency routing enabled, which server will Route 53 direct a user to?

medium

A. The server with the highest weight

B. The server with the lowest latency from the user

C. The server with the most traffic

D. The server randomly chosen

Solution

1. Step 1: Understand latency routing behavior

   Latency routing sends users to the server with the lowest network delay from their location.

2. Step 2: Exclude other options

   Weight is for weighted routing, traffic volume is not a factor, random choice is not latency routing.

3. Final Answer:

   The server with the lowest latency from the user -> Option B

4. Quick Check:

   Latency routing = fastest server [OK]

Hint: Latency routing picks fastest server by user location [OK]

Common Mistakes:

• Mixing weighted and latency routing concepts
• Assuming traffic volume affects routing
• Thinking routing is random

4. You configured weighted routing but all traffic still goes to one server. What is the most likely cause?

medium

A. DNS records have different names

B. Latency routing is enabled instead of weighted

C. Simple routing policy is selected by mistake

D. Weights are set to zero for other servers

Solution

1. Step 1: Check weight values in weighted routing

   If weights for other servers are zero, all traffic goes to the server with non-zero weight.

2. Step 2: Rule out other causes

   Latency routing or simple routing would behave differently; different record names do not affect routing weights.

3. Final Answer:

   Weights are set to zero for other servers -> Option D

4. Quick Check:

   Zero weights = no traffic [OK]

Hint: Check weights are not zero for all servers [OK]

Common Mistakes:

• Confusing routing policy type
• Ignoring zero weights effect
• Assuming DNS names affect weighted routing

5. You want to route 70% of traffic to a primary server and 30% to a backup server, but also ensure users connect to the lowest latency server within those groups. Which routing policy setup should you use?

hard

A. Use latency routing only with weights assigned

B. Use simple routing with latency routing

C. Use weighted routing with latency routing inside each weight group

D. Use weighted routing only without latency

Solution

1. Step 1: Understand combined routing needs

   You want to split traffic by weight, then route users to lowest latency server within each group.

2. Step 2: Identify correct routing policy combination

   Weighted routing controls traffic percentage, latency routing directs users to fastest server inside each weighted group.

3. Step 3: Eliminate incorrect options

   Simple routing cannot split traffic; latency routing alone can't assign weights; weighted routing alone ignores latency.

4. Final Answer:

   Use weighted routing with latency routing inside each weight group -> Option C

5. Quick Check:

   Combine weighted + latency for split and speed [OK]

Hint: Combine weighted and latency routing for split and speed [OK]

Common Mistakes:

• Trying to use simple routing for traffic split
• Ignoring latency inside weighted groups
• Assuming latency routing can split traffic by weight