Examkin

Soru

Zorluk: OrtaOptimizing Network Performance and Latency

A digital health enterprise operates a medical imaging application across multiple AWS accounts. The primary processing workload runs on Amazon EC2 instances in a Production VPC (VPC-A) in the us-east-1 Region. A central reporting application in a Shared Services VPC (VPC-B) in the same Region needs to pull large image files from VPC-A with the lowest possible latency and maximum throughput. Currently, VPC-B accesses the images in VPC-A by routing traffic over the public internet through a NAT Gateway in VPC-B to an Application Load Balancer (ALB) in VPC-A. The network configuration uses a Route 53 Private Hosted Zone (PHZ) for DNS resolution, but resolution is failing from VPC-B.

Which combination of actions will optimize the network performance and resolve the latency and DNS issues? (Select two.)

  1. Establish a VPC Peering connection between VPC-A and VPC-B, configure the VPC route tables to route the inter-VPC traffic through the peering connection, and ensure that the EC2 instances use a Jumbo Frame MTU of 9001.Cevap
  2. Associate the Route 53 Private Hosted Zone from the Production VPC's account with the Shared Services VPC (VPC-B), and verify that DNS resolution and DNS hostnames are enabled in both VPCs.Cevap
  3. C
    Establish an AWS Transit Gateway, configure a Direct Connect Gateway with a Transit VIF to attach both VPCs, and route the traffic transitively through an on-premises connection to bypass the NAT Gateway.
  4. D
    Create a single NAT Gateway in VPC-A to handle inbound traffic from VPC-B, update VPC-B's route tables to point to this NAT Gateway, and configure Route 53 to resolve the ALB via a public alias record.
  5. E
    Submit a support ticket to AWS to pre-warm the ALB in VPC-A for the maximum expected file transfer throughput, and configure the EC2 instances in VPC-B to query the ALB using its public IP address.

Cevap

Establish a VPC Peering connection between the VPCs, configure the route tables, and enable Jumbo Frames (MTU of 9001). Additionally, associate the Route 53 Private Hosted Zone from the Production VPC's account with the Shared Services VPC, ensuring DNS resolution and DNS hostnames are enabled on both VPCs.
Establishing a VPC Peering connection allows traffic to route directly over the AWS private network, bypassing the NAT Gateway and the public internet. This minimizes latency and reduces data transfer costs. Additionally, since the VPCs are in the same Region, VPC Peering supports Jumbo Frames (MTU of 9001), which maximizes throughput for large file transfers. Associating the Route 53 Private Hosted Zone from the Production VPC's account with the Shared Services VPC (VPC-B), while verifying that DNS resolution and DNS hostnames are enabled in both VPCs, allows EC2 instances in VPC-B to resolve the private DNS names of the services in VPC-A.

Adım Adım Çözüm

1
Configure VPC Peering
A direct, private network path between VPC-A and VPC-B is created, allowing traffic to bypass the public internet and NAT Gateway.
Routing traffic directly through a VPC Peering connection minimizes latency, avoids NAT Gateway bandwidth limits, and eliminates NAT Gateway data transfer charges.
2
Enable Jumbo Frames
The MTU on the EC2 instances is set to 9001.
Since the VPCs are in the same Region, VPC Peering supports Jumbo Frames (MTU of 9001), which increases the payload size per packet and maximizes throughput for large image files.
3
Associate the Route 53 Private Hosted Zone
VPC-B is associated with the Private Hosted Zone hosted in the Production VPC's account.
This allows instances in VPC-B to resolve the internal domain names of the resources in VPC-A privately, resolving the DNS resolution failure.

Anahtar Kavram

Optimizing inter-VPC network performance and latency using VPC Peering with Jumbo Frames (MTU 9001) and configuring cross-account Route 53 Private Hosted Zone associations.
Tahmini Süre:3m 0s
Bu soruyu puanla

Konular

Optimizing Network Performance and Latency