A company is planning to migrate its SAP workloads to AWS. The company will use two VPCs. One VPC will be for production systems, and one VPC will be for non-production systems. The company will…

Question

Options

• ACreate an AWS Transit Gateway. Attach the VPCs to the transit gateway. Add the appropriate
• BEstablish a VPC peering connection between the two VPCs. Add the appropriate routes in the
• CCreate an internet gateway in each VPUse an AWS Site-to-Site VPN connection between the two
• DSet up an AWS Direct Connect connection between the two VPCs. Add the appropriate routes in

• A
  2% (1)
• B
  79% (33)
• C
  14% (6)
• D
  5% (2)

Explanation

VPC peering is the most cost-effective solution for connecting two VPCs. AWS does not charge for data transfer between instances in the same Availability Zone over a VPC peering connection. Since the question states that non-production systems and the primary production nodes are all hosted in the same Availability Zone, data transfer costs between the peered VPCs would be zero, making this the cheapest option. AWS Transit Gateway (A) incurs per-hour attachment fees and per-GB data processing charges, making it more expensive and better suited for connecting many VPCs. Using internet gateways with Site-to-Site VPN (C) adds complexity and cost. AWS Direct Connect (D) is designed for on-premises-to-AWS connectivity and is expensive and unnecessary for VPC-to-VPC communication.

No community discussion yet for this question.