Examkin

Soru

Zorluk: Çok zorOptimizing Network Performance and Latency

A logistics and fleet management SaaS platform collects real-time telemetry from delivery vehicles globally. The platform's ingestion tier is deployed in TelemetryIngestVPC in the eu-central-1 Region. The ingested data is processed by a latency-sensitive analytics engine deployed in AnalyticsVPC within the same Region. An on-premises monitoring operations center in Munich connects to AWS via a dedicated 10 Gbps AWS Direct Connect connection terminated at a Direct Connect Gateway (DXGW). The operations center uses internal DNS servers to resolve resources in TelemetryIngestVPC using a Route 53 Private Hosted Zone (PHZ) named fleet.internal. The platform has the following requirements:
- The network path between TelemetryIngestVPC and AnalyticsVPC must support maximum throughput and low latency, utilizing Jumbo Frames (MTU 9001).
- Outbound internet access from both VPCs must be highly available and resilient to Availability Zone outages, while minimizing latency.
- On-premises operators must be able to resolve DNS queries for fleet.internal.

Which of the following architectural designs meets these requirements with the lowest latency and highest throughput?

  1. A
    Establish an Transit Gateway to route all traffic between TelemetryIngestVPC and AnalyticsVPC, and configure the Direct Connect Gateway to handle transitive routing between the VPCs using the on-premises Direct Connect link. Associate the Route 53 Private Hosted Zone fleet.internal with both VPCs. Deploy Route 53 Resolver Inbound Endpoints in TelemetryIngestVPC. Configure independent NAT Gateways in each Availability Zone of both VPCs for outbound internet access.
  2. B
    Establish a VPC Peering connection between TelemetryIngestVPC and AnalyticsVPC to enable direct communication supporting MTU 9001. Deploy Route 53 Resolver Inbound Endpoints in TelemetryIngestVPC across multiple Availability Zones for on-premises DNS forwarding, but do not associate the Route 53 Private Hosted Zone fleet.internal with AnalyticsVPC. Configure independent NAT Gateways in each Availability Zone of both VPCs for outbound internet access.
  3. Establish a VPC Peering connection between TelemetryIngestVPC and AnalyticsVPC. Associate the Route 53 Private Hosted Zone fleet.internal with both VPCs. Deploy Route 53 Resolver Inbound Endpoints across multiple Availability Zones in TelemetryIngestVPC to receive forwarded DNS queries from the on-premises network. Configure independent NAT Gateways in each Availability Zone of both VPCs for outbound internet access.Cevap
  4. D
    Establish a VPC Peering connection between TelemetryIngestVPC and AnalyticsVPC to enable direct communication supporting MTU 9001. Associate the Route 53 Private Hosted Zone fleet.internal with both VPCs. Deploy Route 53 Resolver Inbound Endpoints in TelemetryIngestVPC to receive forwarded DNS queries from the on-premises network. Deploy a single NAT Gateway in one Availability Zone of TelemetryIngestVPC and update the route tables of both VPCs to direct all outbound internet-bound traffic to this NAT Gateway.

Cevap

Establish a VPC Peering connection between TelemetryIngestVPC and AnalyticsVPC, associate the Route 53 Private Hosted Zone fleet.internal with both VPCs, deploy Route 53 Resolver Inbound Endpoints across multiple Availability Zones in TelemetryIngestVPC, and configure independent NAT Gateways in each Availability Zone of both VPCs.
The correct architecture establishes a direct VPC Peering connection between TelemetryIngestVPC and AnalyticsVPC to achieve the lowest latency and highest throughput (supporting Jumbo Frames with MTU 9001). It associates the Route 53 Private Hosted Zone fleet.internal with both VPCs so that DNS resolution works natively in both environments. Furthermore, it deploys Route 53 Resolver Inbound Endpoints across multiple Availability Zones to handle DNS queries forwarded from on-premises, and implements independent NAT Gateways in each Availability Zone of both VPCs to ensure highly available, resilient, and low-latency outbound internet routing without cross-AZ performance penalties.

Adım Adım Çözüm

1
Select the lowest-latency connectivity method between TelemetryIngestVPC and AnalyticsVPC.
VPC Peering is chosen because it supports Jumbo Frames (MTU 9001) for intra-region traffic, routing packets directly without intermediate hops (unlike Transit Gateway, which has additional processing overhead).
To satisfy the requirement of maximum throughput and lowest latency using Jumbo Frames.
2
Configure DNS resolution for both cloud resources and on-premises operators.
Associate the Route 53 Private Hosted Zone (PHZ) fleet.internal with both TelemetryIngestVPC and AnalyticsVPC. Then, set up Route 53 Resolver Inbound Endpoints in TelemetryIngestVPC.
A PHZ must be explicitly associated with a VPC for resources within that VPC to resolve its DNS records. The Inbound Endpoint allows on-premises DNS forwarders to query the PHZ over Direct Connect.
3
Configure highly available and optimized outbound internet access.
Deploy independent NAT Gateways in each Availability Zone (AZ) of both VPCs, and configure subnet route tables to direct internet-bound traffic to the NAT Gateway in the same AZ.
This setup prevents cross-AZ latency and data transfer charges, and ensures that an outage in one Availability Zone does not impact internet access for resources in another zone.

Anahtar Kavram

To optimize inter-VPC performance and latency within the same AWS Region, direct VPC Peering is preferred over transit networks due to native Jumbo Frame (MTU 9001) support and lack of additional transit hops. Furthermore, Private Hosted Zones must be associated with every communicating VPC, and NAT Gateways must be deployed per-AZ to maintain local routing domains and high availability.
Bu soruyu puanla

Konular

Optimizing Network Performance and Latency