An enterprise SaaS company has a multi-region application deployed in us-west-2 and ap-northeast-1 behind Application Load Balancers (ALBs). Users in Asia are reporting high latency and connection instability when connecting to the application's public endpoints. Additionally, the company's on-premises data center in Tokyo is connected to the ap-northeast-1 VPC via an AWS Direct Connect (DX) connection with a Private Virtual Interface (VIF) to a Virtual Private Gateway (VGW). The Solutions Architect must optimize global network performance, reduce latency for end-users, and enable transitive routing from the on-premises data center to both the ap-northeast-1 and us-west-2 VPCs. Which two actions should the Solutions Architect take to meet these requirements?
- Deploy AWS Global Accelerator and associate the regional ALBs with the accelerator to route client traffic over the AWS congestion-free global network.Cevap
- Create an AWS Transit Gateway in both regions, peer the Transit Gateways, and connect the on-premises Direct Connect connection via a Transit VIF to a Direct Connect Gateway attached to the Transit Gateways.Cevap
- CAssociate the Direct Connect Gateway directly with the Virtual Private Gateways (VGWs) of both VPCs using the existing Private VIF to enable transitive routing between the on-premises data center and both regions.
- DSet up a Route 53 Resolver Inbound Endpoint in the ap-northeast-1 VPC to resolve the database domain names without associating the private hosted zone with the ap-northeast-1 VPC.
- EConsolidate all outbound traffic through a single NAT Gateway in each region to minimize routing hops and rely on standard ALB scaling to handle instant, massive traffic spikes.