Amazon Route 53 — DNS & Routing
By Pritesh Yadav 18 min read —
Amazon Route 53 is AWS's managed DNS (Domain Name System) service — it turns human-friendly names like example.com into the IP addresses computers use, and it can also register domain names and run health checks. The "53" refers to DNS port 53. The exam loves to confuse Route 53 (which decides which server a name points to) with CloudFront (which caches content close to users) and with load balancers (which spread traffic across servers). It also tests the many routing policies and the special "alias" record.
Most confused here: Route 53 = DNS routing decisions, not content caching (that's CloudFront) and not server load balancing (that's ELB). Alias record = free AWS-resource pointer that works at the zone apex; CNAME = paid lookup that cannot sit at the root domain. Latency routing = fastest network response; Geolocation = where the user physically is; Failover = swap to a backup when health checks fail.
Q1 A company wants users in Europe to automatically be sent to servers in the Frankfurt Region and users in Asia to servers in Tokyo, choosing whichever Region gives each user the fastest network response time. Which Route 53 routing policy fits best?
- Geolocation routing
- Latency-based routing
- Weighted routing
- Simple routing
Answer: B
Why B is correct: Latency-based routing sends each user to the Region that gives them the lowest network latency (fastest round-trip), which is exactly what "fastest network response time" describes. It measures actual network speed, not just geography.
Why the other options are wrong:
- A — Geolocation routes by the user's physical/legal location (continent, country), which is not the same as the fastest response — the nearest Region by map can still be slower on the network.
- C — Weighted routing splits traffic by percentages you set (e.g. 80/20) for testing, ignoring speed entirely.
- D — Simple routing returns one record (or random values) with no awareness of latency or location.
Common trap: "Send users to the closest Region" sounds like geolocation, but the key phrase "fastest response time" means latency-based routing — geographically closest is not always fastest on the network.
Q2 A team must point their root domain example.com directly at an Application Load Balancer, but they cannot use a CNAME at the top (apex) of the zone. Which Route 53 feature solves this at no extra query cost?
- An alias record
- A CNAME record
- An MX record
- A TXT record
Answer: A
Why A is correct: An alias record is a Route 53-specific record that can point the zone apex (the bare root domain) directly at AWS resources like an ALB, CloudFront, or S3 website endpoint. Route 53 does not charge for alias lookups to AWS resources, unlike standard DNS queries.
Why the other options are wrong:
- B — A CNAME cannot legally exist at the zone apex (the root domain) — that is the exact limitation the question describes.
- C — An MX record only directs email to mail servers, not web traffic to a load balancer.
- D — A TXT record holds text (often for verification or SPF), it does not route traffic to a resource.
Common trap: Candidates default to CNAME because it "maps one name to another," forgetting CNAMEs are forbidden at the root domain. Alias is the AWS answer for apex records.
Q3 During a presentation, an architect says "Route 53 is what makes our website load faster by caching images near users." Why is this statement incorrect?
- Route 53 only registers domain names and does nothing else
- Route 53 caches content, but only for users in the same Region as the origin
- Route 53 caches HTML but never images
- Route 53 is a DNS service that resolves names to addresses; content caching near users is done by CloudFront
Answer: D
Why D is correct: Route 53 is a DNS service — its job is translating domain names into IP addresses and deciding which endpoint a request goes to. Caching content (images, video, files) at edge locations close to users is the role of Amazon CloudFront, a content delivery network (CDN). The two services do completely different jobs.
Why the other options are wrong:
- A — Route 53 does much more than register domains — it also does DNS resolution, health checks, and traffic routing.
- B — Route 53 does not cache content at all, so "caches only in the same Region" is false.
- C — Route 53 caches no content of any type; it returns DNS answers, not files.
Common trap: Route 53 and CloudFront both "make sites work globally," so people blur them. Remember: Route 53 = name-to-address direction; CloudFront = caching content near users.
Q4 A company runs a primary website in one Region and an identical standby site in another. They want Route 53 to automatically send all traffic to the standby only when the primary becomes unhealthy. Which combination achieves this?
- Weighted routing with equal weights
- Multivalue answer routing with two records
- Failover routing with health checks
- Geoproximity routing with bias
Answer: C
Why C is correct: Failover routing is built for active-passive setups: you mark one record as primary and one as secondary, and attach a health check to the primary. While the primary passes its health check, Route 53 sends traffic there; the moment it fails, traffic automatically shifts to the secondary standby. That is exactly the described behavior.
Why the other options are wrong:
- A — Weighted routing splits traffic by percentage continuously; it does not keep the standby idle until a failure.
- B — Multivalue returns several healthy records at once for simple load spreading, not a primary/standby switch on failure.
- D — Geoproximity routes by geographic distance with an adjustable bias, unrelated to automatic failover.
Common trap: Multivalue answer routing also uses health checks, so it looks similar — but it serves all healthy records simultaneously rather than holding a standby in reserve. "Only when primary fails" = Failover.
Q5 A retailer must serve customers in France a French-language site and customers in Japan a Japanese-language site, strictly based on the country the user is browsing from (for content-licensing reasons). Which routing policy is designed for this?
- Latency-based routing
- Geolocation routing
- Weighted routing
- Failover routing
Answer: B
Why B is correct: Geolocation routing makes decisions based on the user's physical/legal location — by continent, country, or even US state. This is the right tool when you must serve different content for legal, licensing, or language reasons tied to where the user actually is.
Why the other options are wrong:
- A — Latency routing optimizes for network speed, not the user's country — a fast network path doesn't guarantee the legally correct content.
- C — Weighted routing splits traffic by percentage and has no concept of user location.
- D — Failover routing only switches between primary and backup on health, ignoring geography.
Common trap: Latency and geolocation both feel "location-based," but only geolocation guarantees a user in a given country gets that country's content. Licensing/compliance keywords point to geolocation, not latency.
Q6 A startup wants to release a new version of its application to just 10% of visitors while 90% continue to the current version, so they can monitor the new version before a full rollout. Which Route 53 routing policy supports this directly?
- Simple routing
- Geoproximity routing
- Weighted routing
- Multivalue answer routing
Answer: C
Why C is correct: Weighted routing lets you assign a numeric weight to each record so traffic is divided by percentage — for example 90 to the old version and 10 to the new one. This makes it the standard choice for gradual rollouts, A/B testing, and canary releases.
Why the other options are wrong:
- A — Simple routing points a name at a single target (or returns values randomly); it cannot enforce a controlled 90/10 split.
- B — Geoproximity routes by geographic distance, not by a chosen traffic percentage.
- D — Multivalue returns multiple healthy records for basic spreading but does not give you precise percentage control.
Common trap: "Split traffic" can be misread as load balancing (ELB's job). Here it's DNS-level percentage control for testing two versions, which is weighted routing.
Q7 What is a Route 53 hosted zone?
- A container that holds the DNS records for a particular domain, telling Route 53 how to route traffic for that domain
- An AWS Region where DNS servers are physically located
- A cache of website content stored at edge locations
- A network firewall that filters incoming DNS requests
Answer: A
Why A is correct: A hosted zone is the collection of DNS records (such as A, CNAME, MX, alias) for one domain like example.com. It is essentially the settings container that tells Route 53 how to answer DNS questions and route traffic for that domain.
Why the other options are wrong:
- B — A hosted zone is a logical record container, not a physical Region or data center location.
- C — Caching content at edge locations is CloudFront, not a hosted zone.
- D — Filtering traffic is the job of security groups, network ACLs, or AWS WAF — not a hosted zone.
Common trap: "Zone" sounds geographic, leading people to think of Availability Zones or Regions. A hosted zone is purely a record container for a domain — no physical location implied.
Q8 A solutions team needs DNS to return several healthy IP addresses at once so client applications can pick one, and it should stop returning any endpoint that fails its health check — without designating a formal primary or backup. Which routing policy best matches?
- Failover routing
- Latency-based routing
- Simple routing
- Multivalue answer routing
Answer: D
Why D is correct: Multivalue answer routing returns multiple records (up to eight healthy ones) in a single DNS response and uses health checks to leave out any unhealthy endpoint. There is no primary/secondary — clients receive several good options and choose one, giving simple availability spreading.
Why the other options are wrong:
- A — Failover specifically defines a primary and a backup, which the question rules out.
- B — Latency routing returns the single lowest-latency Region's record, not a set of several at once.
- C — Simple routing has no health checking, so it would keep returning a dead endpoint.
Common trap: Multivalue is mistaken for a load balancer. It is health-aware DNS that hands back multiple answers — it does not actively distribute or balance load the way ELB does.
Q9 A customer wants a single AWS service to register a brand-new domain name, host its DNS records, and run health checks against their servers. Which service provides all three?
- Amazon CloudFront
- Elastic Load Balancing
- Amazon Route 53
- AWS Global Accelerator
Answer: C
Why C is correct: Route 53 is a domain registrar, an authoritative DNS service, and a health-checking service all in one. You can buy/register a domain, manage its DNS records in a hosted zone, and configure health checks that monitor endpoints — all within Route 53.
Why the other options are wrong:
- A — CloudFront is a content delivery network that caches content near users; it neither registers domains nor hosts DNS zones.
- B — Elastic Load Balancing spreads traffic across servers within AWS; it does not register domains or provide DNS.
- D — Global Accelerator improves traffic routing over the AWS network using anycast IPs but does not register domains or host DNS zones.
Common trap: Global Accelerator and Route 53 both "route traffic globally," but only Route 53 is the DNS and domain-registration service. Domain registration is the giveaway for Route 53.
Q10 What is the key difference between an alias record and a CNAME record in Route 53?
- An alias record can point the zone apex (root domain) to AWS resources and incurs no query charge, while a CNAME cannot be used at the apex
- CNAME records are free while alias records are charged per query
- Alias records only work for email routing; CNAMEs only work for web traffic
- CNAME records can point to AWS resources but alias records cannot
Answer: A
Why A is correct: An alias record is a Route 53 extension that can sit at the zone apex (the bare root domain such as example.com) and point straight to AWS resources like ALB, CloudFront, or S3 — and Route 53 charges nothing for those alias lookups. A standard CNAME cannot be placed at the apex and is treated as a regular (billable) DNS query.
Why the other options are wrong:
- B — It is reversed: alias lookups to AWS resources are free, while CNAME queries are standard billable DNS queries.
- C — Both record types relate to directing traffic to endpoints, not a web-versus-email split.
- D — Alias records are specifically designed to point at AWS resources; that is one of their main advantages.
Common trap: Both records "map one name to another," so people think they are interchangeable. The apex limitation and free AWS-resource lookups are what make alias the AWS-preferred choice.
Q11 An engineer configures a Route 53 health check on a web server. Which statement best describes what a health check actually does?
- It blocks malicious traffic from reaching the web server
- It encrypts DNS queries between the user and Route 53
- It automatically scales the number of web servers based on demand
- It periodically tests whether an endpoint is responding, so Route 53 can route traffic away from unhealthy endpoints
Answer: D
Why D is correct: A Route 53 health check regularly sends requests to an endpoint to confirm it is responding correctly. If the endpoint stops responding, Route 53 can stop returning that endpoint in DNS answers and route users to healthy ones — which is the foundation of failover and multivalue routing.
Why the other options are wrong:
- A — Blocking malicious traffic is the role of AWS WAF, security groups, or Shield — not a DNS health check.
- B — Encrypting DNS is unrelated; a health check only monitors endpoint reachability.
- C — Scaling servers up or down is done by EC2 Auto Scaling, not by Route 53 health checks.
Common trap: "Health check" is also a term used by load balancers and Auto Scaling. In Route 53, it specifically governs whether a DNS record is returned, enabling failover — it does not scale or secure anything.
Q12 A company already uses an Application Load Balancer to distribute requests across many EC2 instances in one Region. They now ask whether Route 53 will further "balance the load across those instances." What is the most accurate response?
- Yes, Route 53 replaces the load balancer and distributes requests to each instance
- Yes, Route 53 monitors CPU on each instance and routes to the least busy one
- No, because Route 53 cannot work together with a load balancer at all
- No, Route 53 handles DNS-level routing of names to endpoints; balancing requests across instances is the load balancer's job
Answer: D
Why D is correct: Route 53 works at the DNS level — it decides which endpoint (such as the load balancer's address) a domain name resolves to. Spreading individual requests across the EC2 instances behind that endpoint is the load balancer's job. The two complement each other but do different work.
Why the other options are wrong:
- A — Route 53 does not replace a load balancer; it cannot distribute individual requests to instances behind an ALB.
- B — Route 53 does not inspect instance CPU or pick the least busy server — that is not how DNS works.
- C — Route 53 absolutely works alongside a load balancer; an alias record commonly points a domain at an ALB.
Common trap: Because both can "route traffic," people think Route 53 load-balances. Route 53 chooses an endpoint via DNS; ELB balances requests across servers behind that endpoint.
Q13 An online service wants users routed to resources based on the geographic distance between the user and the resource, with the ability to deliberately shift more traffic toward one location by adjusting a bias value. Which routing policy provides this?
- Geoproximity routing
- Geolocation routing
- Latency-based routing
- Weighted routing
Answer: A
Why A is correct: Geoproximity routing routes traffic based on the geographic distance between users and your resources, and it uniquely lets you set a "bias" that expands or shrinks the area a given resource serves — letting you intentionally pull more traffic toward one location. The adjustable bias is the distinguishing feature.
Why the other options are wrong:
- B — Geolocation routes by the user's country/continent/state, not by calculated distance, and it has no bias control.
- C — Latency routing chooses the fastest network path, not physical distance, and offers no bias setting.
- D — Weighted routing splits by fixed percentages and has no concept of geographic distance.
Common trap: Geolocation and geoproximity sound nearly identical. Geolocation = the user's location (country/state); geoproximity = distance between user and resource, with an adjustable bias. The word "bias" signals geoproximity.
Q14 A developer needs to simply map www.example.com to a single fixed IP address with no failover, no weighting, and no location logic. Which routing policy is the appropriate, lowest-complexity choice?
- Failover routing
- Weighted routing
- Simple routing
- Latency-based routing
Answer: C
Why C is correct: Simple routing is the default, most basic policy — it maps a domain name to a single resource (such as one IP address) with no health checks, percentages, or location awareness. For a plain one-to-one mapping, it is the correct and lowest-complexity choice.
Why the other options are wrong:
- A — Failover routing adds a primary/backup arrangement with health checks, which is unneeded here.
- B — Weighted routing is for splitting traffic by percentage, which the scenario explicitly does not want.
- D — Latency routing involves multiple Regions and speed measurement, far more than a single fixed mapping requires.
Common trap: Candidates over-think and reach for an advanced policy. When the scenario says "single resource, no extra logic," simple routing is correct — adding complexity is the mistake.
Q15 A global company already serves cached static content through CloudFront, but also wants users automatically directed to a healthy Region if their nearest application Region goes down. Which service should handle the automatic Region failover?
- Amazon CloudFront, by caching the backup Region's content
- Amazon Route 53, using failover routing with health checks
- Amazon S3, by replicating the website to all Regions
- AWS Lambda, by detecting the outage and rerouting users
Answer: B
Why B is correct: Directing users to a different healthy Region when one fails is a DNS routing decision, which Route 53 handles with failover routing plus health checks. CloudFront can sit in front for caching, but the automatic name-to-Region failover decision belongs to Route 53.
Why the other options are wrong:
- A — CloudFront caches and delivers content; it is not the service that performs DNS-level Region failover based on health checks.
- C — S3 replication copies objects between buckets but does not redirect users to a healthy Region during an outage.
- D — Lambda runs code on events but is not the standard, managed way to perform DNS failover — Route 53 is purpose-built for this.
Common trap: Because CloudFront is already "global and in front," people assume it handles failover. Caching and DNS failover are separate jobs — automatic Region switching is Route 53's role.
Q16 Which statement most accurately captures the core role of Amazon Route 53 within the AWS networking stack?
- It is a managed DNS service that translates domain names into IP addresses and routes users to endpoints, and can also register domains and run health checks
- It is a content delivery network that caches files at edge locations to reduce latency
- It is a load balancer that distributes incoming requests evenly across EC2 instances
- It is a virtual private network service that connects on-premises data centers to AWS
Answer: A
Why A is correct: Route 53 is fundamentally a managed, highly available DNS service: it resolves human-readable domain names into IP addresses and decides which endpoint a request reaches, with extra abilities to register domains and perform health checks. That summary captures its true scope.
Why the other options are wrong:
- B — Caching files at edge locations describes CloudFront, the CDN, not Route 53.
- C — Distributing requests across instances is the role of Elastic Load Balancing.
- D — Connecting on-premises networks to AWS is the job of AWS Site-to-Site VPN or Direct Connect.
Common trap: Each wrong option is a real AWS networking service that "moves traffic," making them tempting. Anchor on Route 53 = DNS (names to addresses) to separate it from CloudFront, ELB, and VPN.