SOA-C02 practice question 7 of 10

[Security and Compliance] A SysOps administrator needs to configure the Amazon Route 53 hosted zone for example.com and www.example.com to point to an Application Load Balancer (ALB). Which combination of actions should the SysOps administrator take to meet these requirements? (Select TWO.)

Full set: 557 questions
Answer options
A: Configure anArecordforexample.com to point to the IP address of the ALB.
B: Configure an A record for www.example.com to point to the IP address of the ALB.
C: Configure an alias record for example.com to point to the CNAME of the ALB. Correct answer
D: Configure an alias record for www.example.com to point to the Route 53 example.com record. Correct answer
E: Configure a CNAME record for example com to point to the CNAME of the ALB.
Correct Answer:
C. Configure an alias record for example.com to point to the CNAME of the ALB.; D. Configure an alias record for www.example.com to point to the Route 53 example.com record.
Explanation

Amazon Route 53 utilizes alias records to map domain names to AWS resources like an Application Load Balancer. The DNS protocol strictly prohibits creating standard CNAME records at the zone apex (example.com). Therefore, to map the root domain to the ALB, the SysOps administrator must create a Route 53 alias record pointing directly to the provided DNS name target of the load balancer. To establish the www.example.com subdomain seamlessly, the administrator configures a subsequent alias record that internally routes to the primary example.com alias record within the Route 53 hosted zone. This structured routing strategy ensures efficient, highly available resolution for both the apex and subdomain simultaneously while comprehensively adhering to standard DNS architecture constraints natively enforced by Amazon Route 53.

Why Incorrect

A. Application Load Balancers dynamically scale and their associated IP addresses change continuously over time, rendering static A records pointing to hardcoded IP addresses entirely unreliable and prone to extended outages.
B. Using a static A record mapped to hardcoded IP addresses for the subdomain fails predictably because AWS frequently rotates the underlying IP addresses assigned to active Application Load Balancers internally.
E. The industry standard DNS protocol strictly forbids creating fundamental CNAME records directly at the domain apex, rendering it technologically impossible to accurately map example.com utilizing purely a standard CNAME record.

References

Amazon Route 53 Developer Guide. "Choosing between alias and non-alias records". Section: Alias records limits. (Document ID: AWS-R53-DG-2023)

Amazon Route 53 Developer Guide. "Routing traffic to an ELB load balancer". Section: Zone apex configurations. (Document ID: AWS-R53-ELB-DG)

Scroll to Top