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.