Ends in
00
days
00
hrs
00
mins
00
secs
SHOP NOW

Get $3 OFF ALL CCP, SAA, CDA, and SysOps Video Courses!

Find answers, ask questions, and connect with our
community around the world.

Home Forums AWS AWS Certified Solutions Architect Associate Practice exam 4 Q9

  • hellojellojw

    Member
    November 13, 2023 at 3:56 am

    Category: CSAA – Design Resilient Architectures

    A client is hosting their company website on a cluster of web servers that are behind a public-facing load balancer. The client also uses Amazon Route 53 to manage their public DNS.

    How should the client configure the DNS zone apex record to point to the load balancer?

    Answer: Create an A record aliased to the load balancer DNS name.

    Don’t like this question, the answer just happens to be the “most correct” even though it technically isn’t correct either because it doesnt specify the load balancer is an AWS one, it just says “public-facing”. Are we supposed to assume it’s an AWS one? R53 cant do A+alias records for a non-AWS resources correct?

    • This discussion was modified 8 months, 1 week ago by  hellojellojw.
  • JR-TutorialsDojo

    Administrator
    November 17, 2023 at 9:30 am

    Hi hellojellojw,

    Thanks for your feedback.

    You’re correct in your understanding. Amazon Route 53 does support alias records, which allow you to map your zone apex (e.g., example.com) DNS name to your load balancer DNS name. However, this is specifically for AWS resources. If the load balancer is not an AWS resource, Route 53 wouldn’t be able to create an A record aliased to the load balancer DNS name.

    It appears that the question assumes the load balancer is an AWS resource, although it could have been stated more clearly for better understanding. We have taken note of this feedback and will make necessary updates to ensure that the information provided is more explicit. The changes will be reflected on the portal as soon as possible.

    Regards,
    JR @ Tutorials Dojo

Viewing 1 - 2 of 2 replies

Log in to reply.

Original Post
0 of 0 posts June 2018
Now