Certopolis

AWS Certified Solutions Architect – Associate

Route 53 routing policies: failover, weighted, latency, geo

The routing policy decides how Route 53 answers a DNS query. Failover gives active-passive, weighted splits traffic by proportion, latency picks the AWS Region with the lowest latency, geolocation goes by where the user is, geoproximity by distance with an adjustable bias, and multivalue returns up to eight healthy records at random.

The policies

Simple: one resource for the name. Failover: active-passive. Weighted: traffic in proportions you set; a record's share is its weight divided by the sum of the weights. Latency: resources in several AWS Regions, answer from the Region with the best latency for the user, based on measured AWS latency data that changes over time.

Geolocation: route by the user's continent, country or US state. The smallest matching region wins. Queries from unmapped IPs or locations without a record get no answer unless you create a default record.

Geoproximity: route by the location of users and resources. A bias from 1 to 99 expands the area a resource serves; -1 to -99 shrinks it. IP-based: route by the source IP ranges you know. Multivalue answer: up to eight healthy records selected at random.

Health checks and failover

Active-passive uses the failover policy: Route 53 answers with the primary while it is healthy and with the secondary when it is not. Active-active uses any other policy with health checks; Route 53 drops unhealthy records from answers.

For alias records to AWS resources such as load balancers, set Evaluate Target Health to Yes instead of creating a health check. An alias to an S3 website endpoint must have a record name that matches the bucket name.

In a weighted group, zero-weight records are used only when every nonzero record is unhealthy. If every record in a group is unhealthy, Route 53 treats them all as healthy and still answers, rather than returning no answer.

Multivalue is not a load balancer

Multivalue answer routing lets you attach a health check to each record so only healthy IPs are returned. AWS says it is not a substitute for a load balancer, but it improves uptime and spreads load through DNS.

Where the exam catches people

  • Believing latency routing picks the geographically nearest Region: it uses measured latency data, which changes over time.
  • Believing geolocation sends unmatched users to the nearest record: without a default record, Route 53 returns no answer for them.
  • Believing Route 53 returns nothing when every record is unhealthy: it reverts to treating all records as healthy and answers anyway.
  • Believing a positive geoproximity bias shrinks a resource's area: positive expands it, negative shrinks it.
  • Believing a simple record with several IPs removes failed servers: only health-checked records, such as multivalue, drop unhealthy values.

Written from Amazon Web Services's documentation

Try 3 questions on this

Pick an answer to see why each option is right or wrong.

  1. Six EC2 instances in one Region serve an internal API directly, with no load balancer, and the team is not permitted to add one. Clients resolve one name and connect to whichever address they receive. When an instance fails, clients must stop being sent to it, and traffic should be spread across the healthy instances. Which approach will meet these requirements?

    Right. In the game that’s Renown for your Design Resilient Architectures building.

    Not that one: D is right. In the game your Design Resilient Architectures building would lose a little Renown, and this question would come back later.

  2. A company serves example.com from an Application Load Balancer in one AWS Region, and the domain is hosted in Amazon Route 53. When the application is down, visitors must automatically receive a static maintenance page served from Amazon S3. The company does not want to run any servers for the maintenance page. Which combination of steps should a solutions architect take to meet these requirements? (Select TWO.)

    Right. In the game that’s Renown for your Design Resilient Architectures building.

    Not that one: A,C is right. In the game your Design Resilient Architectures building would lose a little Renown, and this question would come back later.

    Show the full explanation and doc quotes

    A lets the targets behind the load balancer decide; for Application Load Balancers with Evaluate Target Health set to Yes, "Route 53 routes queries to the load balancer based on the health of the target groups that are associated with the load balancer" (Route 53 guide, 'Values specific for failover alias records'). C supplies a secondary that works, because of a naming rule for S3 buckets: "The name of the record must match the name of your Amazon S3 bucket." The same entry adds: "In addition, you must configure the bucket for website hosting." D builds the same thing around a bucket whose name differs from the record, so A,D looks complete and cannot work.

    Written from docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-values-alias-common.html

  3. A company uses Amazon Route 53 geoproximity routing with rules for resources in the US East (N. Virginia) and US West (Oregon) Regions and for a data center in Johannesburg that is identified by latitude and longitude. The company must send more South American users to US East (N. Virginia), and must move users gradually away from the Johannesburg data center before it closes. Which actions should be taken to meet these requirements? (Select TWO.)

    Right. In the game that’s Renown for your Design Resilient Architectures building.

    Not that one: A,E is right. In the game your Design Resilient Architectures building would lose a little Renown, and this question would come back later.

    Show the full explanation and doc quotes

    And "To shrink the size of the geographic region from which Route 53 routes traffic to a resource, specify a negative bias of -1 to -99. Route 53 expands the size of adjacent regions." Lowering the Johannesburg bias in steps moves its users to its neighbours gradually.

    Written from docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-geoproximity.html