A company's SysOps administrator deploys a public Network Load Balancer (NLB) in front of the company's web application. The web application does not use any Elastic IP addresses. Users must access…

Question

Options

• ACreate a Route 53 AAAA record for the NLB.
• BCreate a Route 53 alias record for the NLB.
• CCreate a Route 53 CAA record for the NLB.
• DCreate a Route 53 CNAME record for the NLB.

• A
  5% (1)
• B
  77% (17)
• C
  5% (1)
• D
  14% (3)

Explanation

Option B is correct because Route 53 alias records are specifically designed to point to AWS resources like NLBs, ELBs, CloudFront distributions, and S3 buckets - and unlike CNAME records, alias records are free of charge and can be used at the zone apex (e.g., example.com directly, not just www.example.com).

Why the others are wrong:

• A (AAAA) is an IPv6 address record - it requires a static IP address, which the NLB doesn't have (no Elastic IP is used), so it can't point to the NLB's DNS name.
• C (CAA) is a Certificate Authority Authorization record used to specify which CAs can issue SSL certificates for a domain - it has nothing to do with routing traffic.
• D (CNAME) can technically resolve to the NLB's DNS name, but it incurs per-query charges, cannot be used at the zone apex, and resolves through an extra DNS lookup - making it less efficient and more costly than an alias record.

Memory tip: Think "Alias = AWS-native shortcut" - whenever a question asks you to route to an AWS-managed resource (ELB, NLB, CloudFront, S3) with no static IP, alias records are almost always the correct answer because they're free, work at the apex, and resolve directly within Route 53.

No community discussion yet for this question.