R53 doesn't "follow" anything; it is the resolver that will resolve the initial CNAME and the subsequent A record, leading to two charges should both records be hosted on Route 53.
Your customer should look into making use of Alias records wherever they can if this is a concern to them.
Route 53 DNS queries when CNAME points to an A recordAccepted Answerasked 4 years ago
Route 53 A record with Load Balancer DNS not propagatingAccepted Answerasked 2 months ago
CNAME record problemAccepted Answerasked a month ago
Route 53 DNS Firewall - Wildcard / CNAME issueasked a year ago
CNAME for domain.com without wwwasked 6 years ago
Route 53 domain cname record without hosted zoneAccepted Answerasked a year ago
connecting Route 53 domain to Big Cartelasked 3 years ago
Pointing an A Record and CNAME Record to WIX Not Working, A Record not propagatingasked a year ago
AWS Route 53 A record shows up as CNAME in public DNS lookupsasked 6 months ago
How do I resolve a DNS CNAME conflict from the AWS WordPress Plug-In tool for Cloudfront?asked 10 months ago