Bitzu

SAA-C03 ยท High availability and disaster recovery

Route 53 routing policies and failover

Simple, weighted, latency, failover, geolocation and geoproximity routing, health checks and alias records.

Key points

  • Simple: one resource. Weighted: set proportions (canary).
  • Latency: lowest-latency Region. Failover: active-passive, primary while healthy.
  • Geolocation: continent, country, US state. Geoproximity: distance, optional bias.
  • IP-based: client IP ranges. Multivalue answer: up to 8 healthy records, random.
  • Health checks drop unhealthy endpoints.
  • Alias: AWS resources, works at zone apex (not CNAME), free queries, Evaluate Target Health.

Source: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html

Practice questions

Single choice

Which Route 53 routing policy is designed for an active-passive setup where a standby site receives traffic only when the primary is unhealthy?

  1. Weighted routing
  2. Latency routing
  3. Failover routing
  4. Simple routing
Show answer

Answer: C. Failover routing

Failover routing answers with the primary record while it is healthy and switches to the secondary record when it is not. Weighted and latency routing are used for active-active setups, and simple routing has no health-based switching between records.

Select all that apply

Which statements about Route 53 alias records are true?

  1. They can be created at the zone apex, such as example.com
  2. Queries for alias records that point to AWS resources are not charged
  3. They can point to any hostname hosted at another DNS provider
  4. You set your own TTL when the alias targets a load balancer
  5. dig and nslookup always show them as CNAME records
Show answer

Answer: A. They can be created at the zone apex, such as example.com, B. Queries for alias records that point to AWS resources are not charged

Alias records can be created at the zone apex (example.com), where a CNAME is not allowed, and Route 53 does not charge for alias queries to AWS resources. An alias cannot target an arbitrary domain at another DNS provider (a CNAME can), its TTL comes from the target resource rather than being set by you, and dig shows it as the record type you chose, such as A.

True or false

Latency routing always sends a user to the AWS Region that is geographically closest to them.

Show answer

Answer: False

False. Latency routing chooses the Region with the best network latency for the user, which is not always the nearest one on a map. Routing by where users or resources are located is the job of geolocation and geoproximity routing.

Practice 8 questions on this topic in Bitzu

Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.

Download on the App StoreGet it on Google Play

More SAA-C03 topics in this module