Examkin

Soru

Zorluk: OrtaOptimizing Network Performance and Latency

A financial services company hosts a latency-sensitive trading application on Amazon EC2 instances across two Availability Zones in a VPC in the `us-east-1` Region. The application requires high-throughput, low-latency connectivity to an on-premises database server via an established AWS Direct Connect connection. The application also needs to access external financial market data feeds on the internet, and resolve internal service endpoints in a shared services VPC within the same region using an Amazon Route 53 Private Hosted Zone.

During peak trading hours, the application experiences latency spikes when querying the on-premises database, and instances in the secondary Availability Zone fail to reach the internet when the primary Availability Zone experiences issues. Additionally, instances in the application VPC are unable to resolve the internal endpoints of the shared services VPC.

Which architecture optimization strategy will resolve the latency and connectivity issues while maintaining high availability?

  1. Enable jumbo frames by configuring the MTU to 90019001 on the AWS Direct Connect private virtual interface and the EC2 instances; deploy a NAT Gateway in each Availability Zone public subnet and update the private subnet route tables; and associate the shared services Route 53 Private Hosted Zone with the application VPC.Cevap
  2. B
    Enable jumbo frames by configuring the MTU to 90019001 on the AWS Direct Connect private virtual interface and the EC2 instances; deploy a NAT Gateway in each Availability Zone public subnet; and rely on VPC peering between the VPCs to automatically resolve the shared services DNS endpoints without associating the Private Hosted Zone with the application VPC.
  3. C
    Enable jumbo frames by configuring the MTU to 90019001 on the AWS Direct Connect private virtual interface and the EC2 instances; deploy a single NAT Gateway in the public subnet of the primary Availability Zone and route outbound internet traffic from both Availability Zones to this NAT Gateway; and associate the shared services Route 53 Private Hosted Zone with the application VPC.
  4. D
    Configure transitive VPC-to-VPC routing through the AWS Direct Connect Gateway to enable communication between the application VPC and the shared services VPC; deploy a NAT Gateway in each Availability Zone public subnet; and associate the shared services Route 53 Private Hosted Zone with the application VPC.

Cevap

Enable jumbo frames by configuring the MTU to 90019001 on the AWS Direct Connect private virtual interface and the EC2 instances; deploy a NAT Gateway in each Availability Zone public subnet and update the private subnet route tables; and associate the shared services Route 53 Private Hosted Zone with the application VPC.
The correct strategy optimizes database latency by enabling jumbo frames (90019001 MTU) on both the Direct Connect Private VIF and the EC2 instances. This reduces the number of packets sent and CPU utilization on both ends. High availability and latency optimization for outbound internet traffic are achieved by deploying redundant NAT Gateways across both Availability Zones. Finally, private DNS resolution is enabled by associating the Route 53 Private Hosted Zone with the application VPC.

Adım Adım Çözüm

1
Configure the Maximum Transmission Unit (MTU) to 90019001 on both the AWS Direct Connect Private Virtual Interface (Private VIF) and the Amazon EC2 instances.
Network packets can carry up to 90009000 bytes of payload instead of the standard 15001500 bytes, which reduces packet encapsulation overhead, lowers CPU utilization, and improves database query latency and throughput.
The database queries over the Direct Connect connection are suffering from latency spikes and performance limitations due to packet fragmentation and high packet-per-second processing limits.
2
Deploy a NAT Gateway in the public subnet of each Availability Zone (AZ) and update the private subnet route tables to direct internet-bound traffic (0.0.0.0/00.0.0.0/0) to the local NAT Gateway in the same AZ.
Outbound internet traffic is routed locally within each AZ, avoiding cross-AZ traffic charges and latency, and ensuring that an outage in one AZ does not affect internet connectivity for instances in the other AZ.
The previous configuration used a non-redundant NAT Gateway, causing internet connectivity failure for instances in secondary AZs when the primary AZ experienced issues.
3
Associate the Route 53 Private Hosted Zone (PHZ) from the shared services VPC with the application VPC.
EC2 instances in the application VPC can now successfully resolve the internal endpoints hosted in the shared services VPC.
Route 53 Private Hosted Zones are private by default and are only resolvable within the VPCs they are explicitly associated with.

Anahtar Kavram

Optimizing hybrid and inter-VPC network performance and latency involves choosing correct MTU settings, ensuring local AZ resource redundancy for outbound traffic, and properly associating Route 53 Private Hosted Zones across VPC boundaries.
Bu soruyu puanla

Konular

Optimizing Network Performance and Latency