Examkin

Question

Difficulty: HardOptimizing Network Performance and Latency

A global collaborative engineering SaaS platform hosts its assembly-rendering engine in us-east-1 (VPC-A) and its archive vault in us-west-2 (VPC-B). The VPCs are connected via an inter-region VPC peering connection. The platform's on-premises development center in New York connects to VPC-A via an AWS Direct Connect (DX) connection with a Private Virtual Interface (VIF).

On-premises engineers in London experience severe latency and packet loss when accessing the vault in VPC-B over the public internet. Additionally, internal services in VPC-B cannot resolve the private DNS names of resources in VPC-A, impacting rendering times. The enterprise wants to optimize the network path, reduce latency for London-based engineers, and enable secure, private DNS resolution across both regions.

Which THREE actions should a Solutions Architect take to meet these requirements?

  1. Associate the New York Direct Connect Private VIF with a Direct Connect Gateway (DXGW), and associate the DXGW with the Virtual Private Gateways (VGWs) of both VPC-A and VPC-B.Answer
  2. Deploy AWS Global Accelerator and associate it with a public Application Load Balancer (ALB) in VPC-B, directing London engineers to access the system via the Global Accelerator's static IP addresses.Answer
  3. Enable DNS resolution support for the VPC peering connection, and associate the Route 53 Private Hosted Zone of VPC-A with VPC-B.Answer
  4. D
    Create the Route 53 Private Hosted Zone in VPC-A, enable DNS resolution support on the VPC peering connection, and rely on automatic cross-region peering propagation to resolve the private DNS names in VPC-B.
  5. E
    Route the inter-VPC traffic transitively through the Direct Connect Gateway (DXGW) by configuring the route tables in VPC-A and VPC-B to use the DXGW as the target for the opposing region's CIDR blocks.
  6. F
    Deploy an Application Load Balancer (ALB) in VPC-B to handle engineer connections, and rely solely on the ALB's default dynamic scaling to handle the sudden, massive morning traffic spikes from the London office.

Answer

Associate the New York Direct Connect Private VIF with a Direct Connect Gateway (DXGW) associated with both Virtual Private Gateways; deploy AWS Global Accelerator mapped to a public Application Load Balancer in the destination region; and enable DNS resolution support on the peering connection while associating the Route 53 Private Hosted Zone with the peer VPC.
The correct solution optimizes global user access using AWS Global Accelerator to bypass the public internet, establishes hybrid connectivity to multiple regions via a Direct Connect Gateway associated with Virtual Private Gateways, and resolves name resolution latency by enabling peering DNS support and associating the Private Hosted Zone with the peer VPC.

Step-by-Step Solution

1
Consolidate hybrid access by associating the Private VIF with a Direct Connect Gateway, and attaching the DXGW to the Virtual Private Gateways of both VPCs.
On-premises resources in New York can privately and directly access both the US-East and US-West VPCs over the Direct Connect path.
Direct Connect Gateway facilitates multi-region VPC access over a single Private VIF, eliminating the need for multiple virtual interfaces or traversing the public internet.
2
Configure AWS Global Accelerator to onboard London engineer traffic onto the AWS global network close to their location and route it to an Application Load Balancer in the US-West VPC.
Network latency and packet loss for remote engineers are minimized by bypassing the congested public internet and leveraging the AWS backbone network.
Global Accelerator uses Anycast IP addresses to ingest traffic at the edge location closest to the user, providing a more stable and high-performing network path.
3
Modify the VPC peering connection settings to enable DNS resolution support, and authorize/create the association between the Private Hosted Zone in VPC-A and the peer VPC-B.
Services in VPC-B can successfully resolve private DNS names of resources hosted in VPC-A.
Route 53 Private Hosted Zones require explicit association with target VPCs to allow resolution, and the peering connection must support DNS resolution for hostname queries to succeed across regions.

Key Concept

Optimizing hybrid and multi-region network performance, latency, and DNS resolution by leveraging Direct Connect Gateway, AWS Global Accelerator, and Private Hosted Zone cross-VPC associations.
Rate this question

Topics

Optimizing Network Performance and Latency