An autonomous vehicle telemetry company collects high-frequency sensor data from test vehicles. The data is uploaded to a central on-premises operations center and then replicated to AWS. The AWS environment consists of a primary VPC and spoke VPCs in the `us-west-2` Region, all connected via an AWS Transit Gateway. The on-premises operations center connects to AWS via a AWS Direct Connect connection using a Private Virtual Interface (Private VIF) terminated at a Virtual Private Gateway (VGW) in the primary VPC. Telemetry files average in size and are uploaded via HTTPS. During peak test hours, uploads experience high latency and packet retransmissions, and DNS queries for the internal ingestion API endpoints fail intermittently or take too long to resolve from the spoke VPCs. The solution must maximize throughput, minimize latency, ensure high availability, and avoid unnecessary inter-VPC network hops for DNS resolution. Which two actions should the solutions architect take to meet these requirements?
- Configure a Transit Virtual Interface (Transit VIF) on the Direct Connect connection, associate it with a Direct Connect Gateway connected to the Transit Gateway, and enable Jumbo Frames (MTU ) end-to-end on the Direct Connect connection and Transit Gateway attachments.Cevap
- Associate the Route 53 Private Hosted Zone hosting the telemetry endpoints directly with all spoke VPCs to enable local DNS resolution inside each VPC.Cevap
- CConfigure a Direct Connect Gateway to route transitive traffic directly between the spoke VPCs, bypassing the Transit Gateway to reduce inter-VPC routing overhead.
- DAssociate the Route 53 Private Hosted Zone only with the primary VPC, and route all spoke VPC DNS queries to the primary VPC's inbound resolver endpoint over Transit Gateway attachments.
- ECentralize all outbound public traffic by routing it through a single NAT Gateway deployed in Availability Zone of the primary VPC to simplify route table management.
- FDeploy an Application Load Balancer in the primary VPC to forward ingestion traffic, relying on its default auto-scaling behavior to absorb sudden, massive spikes in telemetry uploads.