A company has a web application that runs in eight AWS Regions. In each Region, the application is hosted on multiple compute resources behind an Application Load Balancer (ALB). The different…

Provisioning an SSL/TLS certificate for the new domain via AWS Certificate Manager (ACM) in a designated region (e.g., us-east-1) is a prerequisite for HTTPS traffic, which all ALBs are configured to accept, and ensures secure communication for the new single domain.

Setting up latency-based routing in Amazon Route 53 for the new domain directly minimizes latency by directing users to the AWS Region and Application Load Balancer (ALB) that offers the lowest network latency from their location, effectively addressing the single domain and low latency requirements.

Creating an alias record for the accelerator in Route 53 is typically done if Global Accelerator is the primary entry point for the new domain, which would conflict with setting up latency-based routing directly to ALBs (option B).

Creating a *standard* accelerator in AWS Global Accelerator is a common and effective approach for global load balancing and latency reduction for general web applications, making it a strong candidate; however, it was not selected as a correct answer.

Creating an SSL/TLS certificate for *each Region* would be necessary if each regional ALB is responsible for its own SSL termination using the new domain, but the solution chosen implies a different (possibly centralized or CloudFront-integrated) certificate strategy in option A.

Creating an AWS Global Accelerator (even a custom routing type, typically for specific routing) allows traffic to traverse the AWS global network, improving performance and minimizing latency by using AWS's optimized network path to the nearest healthy endpoint, complementing other routing strategies, with 'HTTPS listener' referring to directing traffic to HTTPS endpoints.