SAP-C02 · Question #784
A company in the United States (US) has acquired a company in Europe. Both companies use the AWS Cloud. The US company has built a new application with a microservices architecture. The US company…
The correct answer is D. Create one VPC peering connection for each VPC in us-east-2 to the VPC in eu-west-1. Create. The US company needs to connect five VPCs in us-east-2 to one specific VPC in eu-west-1 without allowing access to other VPCs, cross-region, and cost-effectively.
Question
A company in the United States (US) has acquired a company in Europe. Both companies use the AWS Cloud. The US company has built a new application with a microservices architecture. The US company is hosting the application across five VPCs in the us-east-2 Region. The application must be able to access resources in one VPC in the eu-west-1 Region. However, the application must not be able to access any other VPCs. The VPCs in both Regions have no overlapping CIDR ranges. All accounts are already consolidated in one organization in AWS Organizations. Which solution will meet these requirements MOST cost-effectively?
Options
- ACreate one transit gateway in eu-west-1. Attach the VPCs in us-east-2 and the VPC in eu-west-1
- BCreate one transit gateway in each Region. Attach the involved subnets to the regional transit
- CCreate a full mesh VPC peering connection configuration between all the VPCs. Create the
- DCreate one VPC peering connection for each VPC in us-east-2 to the VPC in eu-west-1. Create
How the community answered
(23 responses)- A4% (1)
- B4% (1)
- C17% (4)
- D74% (17)
Why each option
The US company needs to connect five VPCs in `us-east-2` to one specific VPC in `eu-west-1` without allowing access to other VPCs, cross-region, and cost-effectively.
A Transit Gateway cannot attach VPCs from different regions to a single Transit Gateway instance; cross-region connectivity with TGW requires a Transit Gateway in each region peering with each other.
While Transit Gateways can provide cross-region connectivity, using one in each region and peering them would be more complex and significantly more expensive than simple VPC peering for only five source VPCs to one destination VPC.
A full mesh VPC peering would be overly complex and expensive, creating unnecessary connections between all VPCs, which is not required as only one `eu-west-1` VPC needs to be accessed by `us-east-2` VPCs.
Creating individual VPC peering connections between each of the five `us-east-2` VPCs and the single `eu-west-1` VPC allows direct, private network connectivity between these specific VPCs. VPC peering is a cost-effective solution for direct, point-to-point connections between a limited number of VPCs, especially when avoiding transitive routing and keeping costs low.
Concept tested: Cross-region VPC connectivity options
Source: https://docs.aws.amazon.com/vpc/latest/peering/what-is-vpc-peering.html
Community Discussion
No community discussion yet for this question.