A company is planning to connect a remote office to its AWS infrastructure. The office requires permanent and secure connectivity to AWS. The connection must provide secure access to resources in two

Question

Options

• ACreate two transit gateways. Set up one AWS Site-to-Site VPN connection from the remote office
• BSet up one AWS Site-to-Site VPN connection from the remote office to each of the VPCs. Update
• CSet up one AWS Site-to-Site VPN connection from the remote office to one of the VPCs. Set up
• DCreate a transit gateway. Set up an AWS Direct Connect gateway and one Direct Connect

• A
  4% (1)
• B
  85% (23)
• C
  7% (2)
• D
  4% (1)

Explanation

The requirement is secure, permanent connectivity to two VPCs without enabling VPC-to-VPC Option B achieves this by establishing a separate Site-to-Site VPN connection between the remote office and each VPC. Updating each VPC's route tables ensures traffic from the remote office reaches the correct VPC resources, while preventing routing between the VPCs Options involving transit gateways (A and D) would introduce transitive routing capabilities, which violates the requirement of isolation between VPCs. Option C (VPC peering) directly conflicts with the requirement by enabling cross-VPC access. Therefore, option B is the correct solution as it maintains isolation while providing secure VPN

No community discussion yet for this question.