Examkin

Question

Difficulty: MediumOptimizing Network Performance and Latency

A financial services company hosts a latency-sensitive trading application on AWS. The architecture consists of a client-facing VPC in the us-east-1 Region, a client-facing VPC in the us-west-2 Region, and a shared services VPC in us-east-1. Currently, all three VPCs are interconnected using an AWS Transit Gateway. The application developers are reporting two major issues: high network latency during database synchronization between the us-east-1 client VPC and the us-east-1 shared services VPC, and host name resolution failures when the us-west-2 application attempts to access endpoints in the shared services Private Hosted Zone (PHZ). Which two actions should a solutions architect recommend to optimize network performance, reduce latency, and resolve the DNS issues? (Select TWO.)

  1. Establish a direct VPC Peering connection between the us-east-1 client-facing VPC and the us-east-1 shared services VPC.Answer
  2. Associate the Route 53 Private Hosted Zone from the shared services account with both client-facing VPCs.Answer
  3. C
    Route the cross-VPC traffic using an AWS Direct Connect Gateway to enable transitive routing between the accounts.
  4. D
    Direct all outbound and cross-region traffic through a single NAT Gateway in the shared services VPC.
  5. E
    Rely on standard Application Load Balancer auto-scaling to automatically absorb sudden traffic spikes between regions.

Answer

Establish a direct VPC Peering connection between the us-east-1 client-facing VPC and the us-east-1 shared services VPC, and associate the Route 53 Private Hosted Zone from the shared services account with both client-facing VPCs.
Establishing a direct VPC Peering connection between the us-east-1 client VPC and the us-east-1 shared services VPC optimizes network performance by offering the lowest latency and highest bandwidth path without Transit Gateway processing overhead. Associating the Route 53 Private Hosted Zone with the client-facing VPCs in both regions allows local DNS resolution of private endpoints across accounts.

Step-by-Step Solution

1
Analyze regional latency constraints.
Identify that the us-east-1 client-facing VPC and us-east-1 shared services VPC are in the same region, meaning they can benefit from direct VPC Peering to eliminate the latency added by Transit Gateway processing.
VPC Peering does not have intermediate device hops, offering lower latency for intra-region traffic compared to Transit Gateway.
2
Resolve DNS failures for cross-account and cross-region endpoints.
Associate the Route 53 Private Hosted Zone (PHZ) created in the shared services account with the client-facing VPCs in both us-east-1 and us-west-2.
A Private Hosted Zone must be explicitly associated with any VPC that requires resolution of its records, even across accounts and regions.

Key Concept

Bypassing intermediate transit hops via VPC Peering for lowest latency, and cross-account/cross-region Private Hosted Zone association.
Rate this question

Topics

Optimizing Network Performance and Latency