AWS Route 53 Alias vs CNAME
Route 53 Alias records look similar to CNAME records but have some important differences.
Supported ResourcesAlias records support select AWS resourcesElastic load balancers
CloudFront distributions
API Gateway
Elastic Beanstalk
S3 Website
Global Accelerator
VPC Interface Endpoints
Route 53 record in the same zone hosted
Alias records do not supportEC2 DNS endpoint
RDS DNS endpoint
DNS queries can be directed to any DNS record by using a CNAME record
Supports mapping Zone Apex records with Root domains like example.comAlias
CNAME records do not support Zone Apex records
ChargesRoute 53 doesn’t charge for alias queries to AWS resources
Route 53 charges for CNAME queries.
Record TypeAlias records support only A or AAAA record types
CNAME record redirects DNS queries to a record name, regardless of the type of record specified in the DNS query.Route 53 Alias vs CNAME Comparative AWS Certification Exam Practice Question
Questions are collected via the Internet. The answers are marked according to my knowledge and understanding (which may differ from yours).
AWS services are constantly updated and the answers and questions may be out of date soon. So make sure to research accordingly.
AWS exam questions cannot be updated to keep up with AWS updates. This means that even if the underlying feature has been changed, the question may not be updated.
We welcome further feedback, discussion, and correction. Select 2 answersA Alias record can map a DNS name to another Amazon Route 53 DNS.
You can create a CNAME record for your zone apex.
An Amazon Route 53 CNAME Record can point to any DNS record hosted elsewhere.
TTL can be used to set an Alias record on Amazon Route 53.
An Amazon Route 53 Alias Record can point to any DNS records hosted anywhere.
Use an A record
Use an Amazon Route 53 CNAME Record
Amazon Route 53 Alias recordReferences
AWS_Route_53_Alias_CNAME_Comparision