A company uses Amazon Route 53 to manage the public DNS records for the domain example.com. The company deploys an Amazon CloudFront distribution to deliver static assets for a new corporate…

Question

Options

• ACreate a CNAME record.
• BCreate a CNAME record.
• CCreate an A record.
• DCreate an A record.

• A
  13% (6)
• B
  4% (2)
• C
  6% (3)
• D
  77% (37)

Explanation

Option D is correct because Route 53 supports Alias A records, which can point directly to AWS resources like CloudFront distributions - this is the AWS-recommended approach. An Alias A record resolves the CloudFront domain (d1234.cloudfront.net) to its underlying IP addresses without exposing them, handles IP changes automatically, and incurs no additional DNS query charges.

Why the distractors are wrong: Although a CNAME record (A/B) can technically resolve a subdomain to the CloudFront domain name, AWS explicitly recommends Alias records for routing to CloudFront because CNAMEs incur per-query charges and cannot be used at the zone apex - making them less flexible and cost-efficient. A plain A record (C, without the Alias flag) requires a static IP address, which CloudFront does not provide since its edge nodes use dynamic IPs.

Memory tip: Think "Alias for AWS resources." Whenever Route 53 needs to point to a native AWS service (CloudFront, ALB, S3, API Gateway), reach for an Alias A record - it's free, flexible, and fully managed.

No community discussion yet for this question.