An enterprise financial platform operates its core transaction processing engine in private subnets across Availability Zones in the `us-east-1` Region. The workloads must satisfy three networking requirements:
1. Establish high-throughput, low-latency communication with a database cluster located in a separate VPC within the same Region.
2. Query external credit-scoring APIs via the internet with a target latency of less than and high availability.
3. Resolve private DNS hostnames for utility resources hosted in a shared services VPC.
Currently, all private subnets route internet-bound traffic through a single NAT Gateway located in Availability Zone `us-east-1a`, a Transit Gateway is used for VPC-to-VPC routing, and the Route 53 Private Hosted Zones (PHZs) are associated only with the shared services VPC. During high-volume trading hours, users experience query timeouts, increased latency, and host resolution failures.
Which combination of actions will resolve the bottlenecks and optimize network performance?
- ADeploy a NAT Gateway in each of the Availability Zones. Create a Route 53 Resolver outbound endpoint in the transaction processing VPC to forward internal queries to public DNS servers, relying on Route 53 latency-based routing to resolve the private hostnames of the shared services VPC.
- BAssociate the Route 53 PHZ with the transaction processing VPC. To optimize inter-VPC database traffic, replace the Transit Gateway attachments with a Direct Connect Gateway directly attached to both VPCs, and configure BGP routing on the on-premises router to route traffic transitively between them.
- Associate the Route 53 PHZ of the shared services VPC with the transaction processing VPC. Deploy a NAT Gateway in each of the Availability Zones, and update the private subnet route tables to direct internet traffic () to the local NAT Gateway in each respective Availability Zone.Cevap
- DAssociate the Route 53 PHZ with the transaction processing VPC. To handle the external API traffic, configure an Auto Scaling group to horizontally scale the single NAT Gateway in `us-east-1a` based on network throughput metrics, and update the route tables of all subnets to point to the scaling group.