Routing policies (simple, weighted, latency) in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does a simple routing policy behave in AWS Route 53?

You have a Route 53 record with a simple routing policy pointing to a single IP address. What happens when a user queries this DNS record?

A The DNS query returns multiple IP addresses in a round-robin fashion.

B The DNS query returns the single IP address every time.

C The DNS query returns IP addresses based on the user's geographic location.

D The DNS query returns IP addresses weighted by traffic percentage.

💡 Hint

Simple routing returns one fixed answer.

Simple routing returns the single value configured for the DNS record every time a query is made.

❓ Architecture

intermediate

Weighted routing policy distribution

You configure two Route 53 records with weighted routing: one with weight 70 and the other with weight 30. What is the expected behavior when users query this DNS record?

A 70% of queries return the first record's IP, 30% return the second record's IP.

B All queries return the IP of the record with the higher weight.

C Queries are routed based on the lowest latency between user and record.

D Queries are routed randomly without considering weights.

💡 Hint

Weighted routing splits traffic based on weights.

Weighted routing distributes DNS responses according to the weights assigned to each record, roughly matching the percentage of traffic.

❓ service_behavior

advanced

Latency routing policy behavior

You have two AWS regions with Route 53 latency routing records. A user in Europe queries the DNS. Which IP address will Route 53 return?

A The IP address of the region with the lowest latency to the user in Europe.

B The IP address of the region with the highest weight assigned.

C The IP address of the region closest geographically to the user, ignoring latency.

D The IP address of the region with the most health checks passing.

💡 Hint

Latency routing chooses the fastest region for the user.

Latency routing returns the IP address of the AWS region that provides the lowest network latency to the user.

❓ security

advanced

Impact of health checks on weighted routing

In a weighted routing setup with two records, one record's health check fails. What happens to DNS queries?

A DNS queries fail with an error until the unhealthy record recovers.

B DNS queries continue to be routed based on weights, ignoring health checks.

C DNS queries are routed randomly between both records.

D All DNS queries are routed to the healthy record regardless of weights.

💡 Hint

Health checks remove unhealthy endpoints from routing.

When a health check fails, Route 53 stops routing traffic to that record, sending all queries to healthy records.

🧠 Conceptual

expert

Combining latency and weighted routing policies

You want to route traffic to two AWS regions using latency routing but also want to control traffic distribution with weights. Which approach is valid?

A Create weighted routing records for each region, then create latency records as children of weighted records.

B Use latency routing for regions and assign weights directly to latency records; Route 53 supports this combination.

C Route 53 does not support combining latency and weighted routing policies on the same DNS name.

D Create latency routing records for each region, then create weighted records as children of latency records.

💡 Hint

Route 53 routing policies are mutually exclusive per record name.

Route 53 does not allow combining latency and weighted routing policies on the same DNS record name. You must choose one routing policy per record name.