Examkin

Soru

Zorluk: ZorOptimizing Network Performance and Latency

A global SaaS platform hosts its ingestion service in a VPC in the us−west−2us-west-2 Region and its reporting dashboard in a VPC in the us−east−1us-east-1 Region. The ingestion service runs behind an internal Application Load Balancer (ALB) and is associated with a Route 53 Private Hosted Zone (PHZ) `ingest.local`. Currently, the two VPCs are connected via AWS Transit Gateway peering across the regions. The reporting dashboard makes millions of query requests daily to the ingestion service, resulting in high latency and significant inter-region data transfer charges due to Transit Gateway processing fees. The reporting dashboard must resolve the private DNS names of the ingestion service and connect securely over the AWS network with the lowest possible latency and cost. Which combination of actions should a Solutions Architect implement to optimize the network performance and reduce costs? (Select TWO.)

  1. Establish an inter-region VPC Peering connection directly between the reporting VPC in us-east-1 and the ingestion VPC in us-west-2, and update the route tables to route the traffic across the peering connection.Cevap
  2. Associate the Route 53 Private Hosted Zone ingest.local with the reporting VPC in us-east-1, ensuring the reporting dashboard resolves queries directly to the private IP addresses of the ingestion ALB.Cevap
  3. C
    Associate the Private Hosted Zone ingest.local with the Transit Gateway in us-west-2 to automatically enable DNS resolution for all peered VPCs across both regions.
  4. D
    Create a Direct Connect Gateway and establish an IPSec VPN over a Transit VIF to route the inter-VPC traffic transitively through the customer's on-premises network data center.
  5. E
    Deploy a single NAT Gateway in the reporting VPC in us-east-1, configure the route tables to route all ingestion traffic through this NAT Gateway to the public IP addresses of the ingestion ALB, and request AWS Support to pre-warm the ALB.

Cevap

Establish an inter-region VPC Peering connection directly between the reporting VPC and the ingestion VPC, and associate the Route 53 Private Hosted Zone with the reporting VPC.
Establishing a direct inter-region VPC Peering connection provides the shortest network path (lowest latency) over the AWS backbone and avoids Transit Gateway processing fees. Associating the Route 53 Private Hosted Zone with the reporting VPC in the secondary region ensures that private DNS resolution functions correctly, directing traffic to the private IP addresses of the ingestion Application Load Balancer.

Adım Adım Çözüm

1
Analyze the current traffic path and overhead.
The current path traverses AWS Transit Gateway peering, which introduces additional processing hops and data processing charges in each region, increasing latency and cost.
Identifying the root cause of high latency and cost allows for direct path optimization.
2
Select a direct network routing option.
Establishing an inter-region VPC Peering connection provides a direct, horizontal communication path over the AWS backbone with no Transit Gateway processing overhead.
Direct VPC Peering offers the lowest possible latency and eliminates Transit Gateway-specific data processing costs.
3
Configure DNS resolution for cross-region private communication.
Associate the Private Hosted Zone (PHZ) ingest.local with the reporting VPC in us-east-1.
Route 53 Private Hosted Zones must be associated with any VPC that needs to resolve its private records, allowing the reporting dashboard to resolve the ingestion ALB's private IP addresses.

Anahtar Kavram

Optimizing latency and costs for inter-region VPC communications using direct VPC Peering and cross-region Private Hosted Zone associations.
Bu soruyu puanla

Konular

Optimizing Network Performance and Latency