A company runs a web application that users access using the name www example com. The company manages the domain name example.com using Amazon Route 53. The company created an Amazon CloudFront…

Question

Options

• ACreate a CNAME record in Amazon Route 53 that points to the CloudFront distribution URL.
• BCreate an ALIAS record in Amazon Route 53 that points to the CioudFront distribution URL.
• CCreate an A record in Amazon Route 53 that points to the public IP address of the web
• DCreate a PTR record in Amazon Route 53 that points to the public IP address of the web

• A
  5% (2)
• B
  78% (29)
• C
  14% (5)
• D
  3% (1)

Explanation

Option B is correct because Route 53 ALIAS records are a native AWS feature that can point to CloudFront distributions (and other AWS resources like ELBs and S3 buckets) at no additional cost - Route 53 does not charge for ALIAS record queries to AWS endpoints, making it the most cost-effective choice.

Why the distractors are wrong:

• A (CNAME): A CNAME cannot be used at the zone apex (e.g., example.com itself), and Route 53 charges for CNAME queries - making it both technically limited and more expensive than ALIAS.
• C (A record with public IP): CloudFront does not expose a static public IP; its IPs can change, so hardcoding an IP would break the application and is not a supported approach.
• D (PTR record): PTR records are for reverse DNS lookups (IP → domain name), not for routing user traffic to a resource - entirely the wrong record type.

Memory tip: Think "ALIAS = AWS's gift to you" - it's free for AWS-to-AWS routing, works at the zone apex where CNAME cannot, and is always the preferred answer when pointing Route 53 to a CloudFront distribution, ELB, or S3 website endpoint.

No community discussion yet for this question.