Route 53 with ELB integration in AWS - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does Route 53 integrate with an Elastic Load Balancer (ELB)?

Which statement best describes how Amazon Route 53 works with an Elastic Load Balancer (ELB)?

A Route 53 creates an alias record that points directly to the ELB's DNS name, allowing seamless traffic routing without needing an IP address.

B Route 53 requires you to manually enter the ELB's IP addresses as A records to route traffic correctly.

C Route 53 cannot route traffic to ELB; you must use a third-party DNS service for ELB integration.

D Route 53 uses CNAME records to point to the ELB's IP addresses for routing traffic.

💡 Hint

Think about how Route 53 handles dynamic IP addresses of ELB.

Route 53 uses alias records to point to ELB DNS names. This avoids the need to manage IP addresses, which can change.

❓ Configuration

intermediate

Identify the correct Route 53 record configuration for ELB integration

You want to route traffic from your domain example.com to an Application Load Balancer (ALB) using Route 53. Which Route 53 record configuration is correct?

A Create an A record with alias enabled, selecting the ALB from the dropdown list in Route 53 console.

B Create a CNAME record pointing to the ALB's IP address.

C Create an MX record pointing to the ALB's DNS name.

D Create a TXT record with the ALB's DNS name as the value.

💡 Hint

Alias records are special Route 53 records for AWS resources.

Alias A records allow routing to AWS resources like ALB without using IP addresses or CNAMEs at the root domain.

❓ Architecture

advanced

Designing a highly available web application with Route 53 and ELB

You need to design a web application architecture that is highly available across two AWS regions using Route 53 and ELB. Which approach ensures traffic is routed to the healthiest region automatically?

A Use Route 53 geolocation routing without health checks to route traffic based on user location only.

B Use Route 53 latency-based routing with health checks on ELBs in both regions to route traffic to the region with the lowest latency and healthy ELB.

C Use Route 53 simple routing with a single ELB in one region and manually switch DNS records during failure.

D Use Route 53 weighted routing without health checks to distribute traffic evenly between regions.

💡 Hint

Consider routing that adapts to both latency and health status.

Latency-based routing with health checks ensures traffic goes to the fastest and healthy ELB, improving availability and performance.

❓ security

advanced

Securing DNS traffic between Route 53 and ELB

Which practice improves security when integrating Route 53 with an ELB for a public web application?

A Disable HTTPS on ELB to simplify traffic inspection.

B Use a private hosted zone in Route 53 for the public domain to restrict access.

C Enable DNSSEC signing on the Route 53 hosted zone to protect DNS queries from tampering.

D Configure ELB to accept traffic only from Route 53 IP addresses.

💡 Hint

Think about protecting DNS query integrity.

DNSSEC adds a layer of security by digitally signing DNS data, preventing attackers from spoofing DNS responses.

❓ service_behavior

expert

Understanding Route 53 alias record behavior with ELB DNS changes

If the IP addresses behind an ELB change, what happens to Route 53 alias records pointing to that ELB's DNS name?

A Route 53 alias records convert to CNAME records automatically to handle IP changes.

B Route 53 alias records break and require manual update with new IP addresses.

C Route 53 alias records cache the old IP addresses for 24 hours before updating.

D Route 53 alias records automatically resolve to the new IP addresses without any manual update required.

💡 Hint

Consider how alias records abstract IP management.

Alias records point to ELB DNS names, so when ELB IPs change, Route 53 resolves the DNS name dynamically, requiring no manual updates.

Practice

1. What is the main benefit of using a Route 53 alias record with an Elastic Load Balancer (ELB)?

easy

A. It allows you to point your domain directly to the ELB without using an IP address.

B. It automatically creates a backup server for your website.

C. It encrypts all traffic between users and the ELB.

D. It reduces the cost of running the ELB.

Solution

1. Step 1: Understand Route 53 alias records

   Alias records let you point your domain name to AWS resources like ELB without needing an IP address.

2. Step 2: Recognize ELB integration benefit

   This simplifies DNS management and handles ELB IP changes automatically.

3. Final Answer:

   It allows you to point your domain directly to the ELB without using an IP address. -> Option A

4. Quick Check:

   Alias record points domain to ELB without IP [OK]

Hint: Alias records link domains to ELB without IPs [OK]

Common Mistakes:

• Thinking alias records create backups
• Confusing alias with encryption
• Assuming alias reduces ELB cost

2. Which of the following is the correct way to create a Route 53 alias record pointing to an ELB in the AWS console?

easy

A. Create a CNAME record pointing to the ELB's IP address.

B. Create an A record and enter the ELB's IP address manually.

C. Create an A record and select 'Alias' with the ELB as the target.

D. Create a TXT record with the ELB's DNS name.

Solution

1. Step 1: Know Route 53 record types for ELB

   ELB does not have fixed IPs, so you cannot use IP addresses directly.

2. Step 2: Use alias A record

   Route 53 allows creating an A record with alias enabled, selecting the ELB DNS name as target.

3. Final Answer:

   Create an A record and select 'Alias' with the ELB as the target. -> Option C

4. Quick Check:

   Alias A record points to ELB DNS [OK]

Hint: Use alias A record, not IP or CNAME for ELB [OK]

Common Mistakes:

• Using IP address for ELB
• Choosing CNAME instead of alias A record
• Using TXT record incorrectly

3. Given a Route 53 setup with an alias record pointing to an ELB, what happens if the ELB becomes unhealthy and fails its health checks?

medium

A. Route 53 continues sending traffic to the ELB regardless of health status.

B. Route 53 automatically stops sending traffic to the ELB until it is healthy again.

C. Route 53 deletes the alias record automatically.

D. Route 53 redirects traffic to a backup IP address.

Solution

1. Step 1: Understand Route 53 health checks with ELB

   Route 53 alias records pointing to ELB do not automatically stop sending traffic if the ELB is unhealthy because ELB manages its own health and traffic routing internally.

2. Step 2: Behavior on ELB failure

   Route 53 continues to resolve the alias record to the ELB DNS name regardless of ELB health status; ELB itself stops routing traffic to unhealthy targets.

3. Final Answer:

   Route 53 continues sending traffic to the ELB regardless of health status. -> Option A

4. Quick Check:

   Route 53 alias records do not perform health-based routing for ELB [OK]

Hint: ELB manages health; Route 53 alias does not stop traffic [OK]

Common Mistakes:

• Thinking Route 53 stops traffic to unhealthy ELB
• Assuming Route 53 deletes records on failure
• Believing Route 53 redirects to IP automatically

4. You created a Route 53 alias record to an ELB, but your website is not reachable. Which of the following is the most likely cause?

medium

A. The domain name is missing a trailing dot in the alias record.

B. The alias record is set as a CNAME instead of an A record with alias enabled.

C. The alias record points to the ELB DNS name, but the ELB is in a different AWS region than the hosted zone.

D. The ELB does not have any registered healthy targets.

Solution

1. Step 1: Check ELB target health

   If ELB has no healthy targets, it cannot serve traffic, causing website unreachable.

2. Step 2: Verify alias record and region

   Alias records can point across regions; CNAME is invalid for alias; trailing dot is not required for alias.

3. Final Answer:

   The ELB does not have any registered healthy targets. -> Option D

4. Quick Check:

   Healthy targets needed for ELB to serve traffic [OK]

Hint: Check ELB target health if site unreachable [OK]

Common Mistakes:

• Confusing alias record type
• Assuming region mismatch breaks alias
• Thinking trailing dot is required

5. You want to configure Route 53 to route traffic to two ELBs in different regions for high availability. Which setup ensures traffic is sent only to healthy ELBs and balances load between them?

hard

A. Create two CNAME records with the same domain name pointing to each ELB's DNS name.

B. Create two alias A records with the same domain name, each pointing to one ELB, and enable health checks on both records.

C. Create a single alias A record pointing to the ELB in the primary region and manually switch to the other ELB if failure occurs.

D. Create two alias A records with different domain names and use a third DNS service to balance traffic.

Solution

1. Step 1: Use alias A records with health checks

   Route 53 supports multiple alias records with health checks to route traffic only to healthy ELBs.

2. Step 2: Load balancing across regions

   By creating two alias records with health checks, Route 53 can balance traffic and failover automatically.

3. Final Answer:

   Create two alias A records with the same domain name, each pointing to one ELB, and enable health checks on both records. -> Option B

4. Quick Check:

   Multiple alias records + health checks = HA and load balancing [OK]

Hint: Use multiple alias records with health checks for HA [OK]

Common Mistakes:

• Using CNAME for ELB alias
• Manual failover instead of health checks
• Using different domain names for ELBs