Examkin

Question

Difficulty: HardOptimizing Network Performance and Latency

An enterprise runs a high-throughput, latency-sensitive SaaS platform across three AWS accounts in the us−east−1us-east-1 Region: a Production account, a Data Analytics account, and a Shared Services account. The Production VPC and Data Analytics VPC need to query a centralized, high-performance Amazon ElastiCache cluster hosted in the Shared Services VPC.

Currently, all VPCs are interconnected using an AWS Transit Gateway, but the application teams are reporting latency overhead and high network data processing costs. In addition, applications in the Production and Data Analytics VPCs are experiencing DNS resolution failures when attempting to resolve the cache cluster's domain name, which is managed via a Route 53 Private Hosted Zone (cache.internalcache.internal) created in the Shared Services account.

Which of the following actions should the Solutions Architect take to optimize network performance, minimize latency, and resolve the DNS issues? (Select TWO.)

  1. Establish direct VPC Peering connections between the Shared Services VPC and the other two VPCs, and update the route tables to route traffic directly over the peered connections.Answer
  2. Authorize the Route 53 Private Hosted Zone association from the Shared Services account, and associate the private hosted zone with both the Production VPC and the Data Analytics VPC.Answer
  3. C
    Deploy Route 53 Resolver inbound and outbound endpoints in each VPC, and configure a forwarding rule to resolve the private hosted zone domain across the accounts.
  4. D
    Route all inter-VPC traffic through a centralized, single NAT Gateway in the Shared Services VPC to manage caching traffic and security policies.
  5. E
    Configure a Direct Connect Gateway to route transitive traffic between the spoke VPCs, and submit a ticket to AWS Support to pre-warm the network endpoints.

Answer

To optimize network performance, minimize latency, and resolve the DNS issues, the Solutions Architect should establish direct VPC Peering connections between the Shared Services VPC and the other two VPCs, and authorize the association of the Route 53 Private Hosted Zone from the Shared Services account to associate it directly with both the Production VPC and the Data Analytics VPC.
Establishing direct VPC Peering connections provides the lowest latency and highest throughput without Transit Gateway hop overhead or processing fees. Authorizing and associating the Route 53 Private Hosted Zone across accounts allows native, local DNS resolution for the cache cluster without expensive and high-latency endpoints.

Step-by-Step Solution

1
Replace the Transit Gateway routing path with direct VPC Peering connections between the Shared Services VPC and both the Production and Data Analytics VPCs, then update the VPC route tables.
Traffic between the application servers and the ElastiCache cluster bypasses the Transit Gateway, eliminating the extra gateway hop and Transit Gateway processing fees.
VPC Peering provides direct, unconstrained network pathways within the AWS global network, yielding the lowest possible latency and highest throughput.
2
Authorize the association of the Route 53 Private Hosted Zone in the Shared Services account with the Production VPC and Data Analytics VPC, and associate them.
The Route 53 Resolvers in the Production and Data Analytics VPCs can resolve queries for the caching domain directly and locally.
Direct Private Hosted Zone association resolves DNS queries natively within the VPCs, bypassing the cost, complexity, and latency of Resolver endpoints.

Key Concept

Optimizing multi-account network latency and DNS resolution using VPC Peering and cross-account Private Hosted Zone association.
Estimated Time:3m 0s
Rate this question

Topics

Optimizing Network Performance and Latency