A global maritime logistics enterprise operates its vessel tracking and telemetry ingestio… — AWS Certified Solutions Architect - Professional

A global maritime logistics enterprise operates its vessel tracking and telemetry ingestion system in the AWS Cloud. The ingestion workload runs on Amazon EC2 instances deployed in private subnets across three Availability Zones ( $us-east-1a$ , $us-east-1b$ , and $us-east-1c$ ) in a Production VPC. The EC2 instances must frequently query a high-performance mapping and routing API hosted in a Shared Services VPC in the same region, which is resolved via an Amazon Route 53 Private Hosted Zone (PHZ) named `internal.logistics.aws` managed in a Central Network AWS account.

During peak operation windows, the operations team identifies multiple network performance issues:
- Telemetry ingestion experiences intermittent packet drops and latency spikes when downloading ocean-weather data from external public API endpoints. Currently, all private subnets route outbound traffic ( $0.0.0.0/0$ ) through a single NAT Gateway located in $us-east-1a$ .
- High-frequency queries to the mapping API in the Shared Services VPC experience throughput limitations of $50\text{ Gbps}$ and latency overhead due to routing through an AWS Transit Gateway.
- EC2 instances in the Production VPC occasionally fail to resolve `internal.logistics.aws` or resolve it to its public endpoint instead of the internal Network Load Balancer (NLB) IP address, leading to routing over the public internet.

The enterprise requires a highly available network architecture that optimizes inter-VPC throughput, minimizes latency, removes egress bottlenecks, and ensures correct internal DNS resolution.

Which of the following optimization strategies should a solutions architect implement to meet these requirements?

A
Establish a local VPC Peering connection between the Production VPC and the Shared Services VPC to bypass Transit Gateway bandwidth limits. Keep the single NAT Gateway in $us-east-1a$ but update the route tables of the private subnets in $us-east-1b$ and $us-east-1c$ to point their default routes ( $0.0.0.0/0$ ) to the $us-east-1a$ NAT Gateway's network interface directly. Associate the Route 53 Private Hosted Zone (`internal.logistics.aws`) with the Production VPC.
B
Establish a local VPC Peering connection between the Production VPC and the Shared Services VPC to enable Jumbo Frames up to $9001\text{ bytes}$ MTU. Deploy a NAT Gateway in each of the three Availability Zones in the Production VPC and update the private route tables. Enable DNS resolution support on the VPC Peering connection to resolve the `internal.logistics.aws` domain without associating the Private Hosted Zone with the Production VPC.
Establish a local VPC Peering connection between the Production VPC and the Shared Services VPC to bypass the Transit Gateway bandwidth limits and support Jumbo Frames up to $9001\text{ bytes}$ MTU. Deploy a NAT Gateway in each of the three Availability Zones in the Production VPC, and update the private route tables to route local Availability Zone traffic through its corresponding local NAT Gateway. Associate the Route 53 Private Hosted Zone (`internal.logistics.aws`) with the Production VPC.Answer
D
Establish an AWS Direct Connect connection with a Direct Connect Gateway, and attach both the Production VPC and the Shared Services VPC to the Direct Connect Gateway to route inter-VPC traffic over the private virtual interface, bypassing Transit Gateway limits. Deploy a NAT Gateway in each Availability Zone, and associate the Route 53 Private Hosted Zone (`internal.logistics.aws`) with the Production VPC.

Answer

The strategy that establishes a local VPC Peering connection to support Jumbo Frames, deploys a NAT Gateway in each Availability Zone for redundancy, and associates the Route 53 Private Hosted Zone with the Production VPC.

Establishing a local VPC Peering connection provides a direct path between the VPCs, bypassing the 50 Gbps Transit Gateway bandwidth constraint per VPC attachment and supporting Jumbo Frames (9001 bytes MTU), which reduces latency and serialization overhead. Deploying a NAT Gateway in each Availability Zone eliminates the single-point-of-failure and the performance bottleneck of routing all egress traffic through a single NAT Gateway. Associating the central Route 53 Private Hosted Zone with the Production VPC ensures that queries resolve locally to the internal Network Load Balancer IP address rather than routing over the public internet.

Step-by-Step Solution

Establish a local VPC Peering connection between the Production VPC and the Shared Services VPC.

Provides direct, high-bandwidth (no 50 Gbps limit) and low-latency communication with Jumbo Frame support (up to 9001 bytes MTU) between the two VPCs.

Reduces latency and fragmentation by bypassing the Transit Gateway and enabling full MTU payload transmissions.

Deploy redundant NAT Gateways across all three Availability Zones and update subnet route tables.

Outbound internet traffic routes locally within each Availability Zone, removing cross-AZ latency and eliminating the single NAT Gateway bottleneck.

Ensures high availability and optimizes egress performance for weather API queries during peak windows.

Associate the Route 53 Private Hosted Zone internal.logistics.aws from the Central Network account with the Production VPC.

Enables instances in the Production VPC to natively resolve the private DNS names to the internal Network Load Balancer IP address.

Prevents name resolution failures and avoids public DNS routing over the internet.

Key Concept

VPC Peering MTU, NAT Gateway redundancy, and cross-account Route 53 PHZ association for network performance optimization.

Estimated Time:3m 0s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics