Examkin

Question

Difficulty: MediumOptimizing Network Performance and Latency

An enterprise operates a high-traffic financial platform. The application tier is deployed in private subnets across multiple Availability Zones in an Application VPC, which is connected to a Transit Gateway. A Shared Services VPC hosts a centralized outbound NAT Gateway and a Route 53 Private Hosted Zone (PHZ) for internal service discovery. Users report intermittent latency spikes and connection timeouts. A network audit reveals that outbound traffic to external financial APIs from all Availability Zones in the Application VPC routes through a single NAT Gateway in the Shared Services VPC. Additionally, internal DNS queries for services in the PHZ fail to resolve from the Application VPC, and sudden traffic spikes during market open cause the Application Load Balancer (ALB) to drop connections. Which combination of actions should the Solutions Architect implement to optimize network performance, minimize latency, and resolve these issues?

  1. Associate the Route 53 Private Hosted Zone with the Application VPC to enable local DNS resolution. Deploy a NAT Gateway in each Availability Zone within the Shared Services VPC and configure the routing tables accordingly. Request AWS Support to pre-warm the Application Load Balancer prior to market open events.Answer
  2. B
    Configure Transit Gateway route propagation to automatically share DNS resolution records between VPCs. Deploy a NAT Gateway in each Availability Zone within the Shared Services VPC and configure the routing tables accordingly. Request AWS Support to pre-warm the Application Load Balancer prior to market open events.
  3. C
    Associate the Route 53 Private Hosted Zone with the Application VPC to enable local DNS resolution. Retain the single NAT Gateway in the Shared Services VPC to centralize outbound traffic flow and save costs, while using cross-zone load balancing. Request AWS Support to pre-warm the Application Load Balancer prior to market open events.
  4. D
    Associate the Route 53 Private Hosted Zone with the Application VPC to enable local DNS resolution. Deploy a NAT Gateway in each Availability Zone within the Shared Services VPC and configure the routing tables accordingly. Rely on the default auto-scaling behavior of the Application Load Balancer to handle the market open traffic spikes.

Answer

Associate the Route 53 Private Hosted Zone with the Application VPC, deploy NAT Gateways in each Availability Zone within the Shared Services VPC, and request AWS Support to pre-warm the Application Load Balancer before market open events.
The correct option optimizes performance and minimizes latency by implementing three key practices: associating the Route 53 Private Hosted Zone directly with the Application VPC to allow immediate and local resolution of internal domains; deploying redundant NAT Gateways across all active Availability Zones to keep outbound traffic local to each zone and remove cross-AZ network latency; and pre-warming the Application Load Balancer to guarantee that the sudden influx of connections at market open is handled smoothly without dropped packets.

Step-by-Step Solution

1
Associate the Route 53 Private Hosted Zone with the Application VPC.
Instances in the Application VPC resolve internal service endpoints locally and successfully.
Route 53 Private Hosted Zones are private by default and must be explicitly associated with any VPC that requires resolution of their records.
2
Deploy NAT Gateways in each Availability Zone in the Shared Services VPC and update route tables.
Outbound traffic to external APIs remains within the same Availability Zone, minimizing latency and eliminating a single point of failure.
Routing all cross-AZ traffic through a single NAT Gateway introduces latency and creates a single point of failure.
3
Submit a pre-warming request to AWS Support for the Application Load Balancer.
The Application Load Balancer is pre-scaled to handle the anticipated surge of connections at market open without dropping requests.
Standard auto-scaling is reactive and cannot scale fast enough to meet instantaneous flash traffic demands.

Key Concept

Minimizing network latency and optimizing performance in hybrid and multi-account architectures by implementing multi-AZ NAT Gateway redundancy, proper private DNS association, and proactive load balancer scaling.
Rate this question

Topics

Optimizing Network Performance and Latency