A global company uses an organization in AWS Organizations to manage multiple AWS accounts. To comply with regulations, the company deploys workload environments to five AWS Regions. The company has a

Question

Options

• ACreate a transit gateway in the central shared AWS account. Share the transit gateway with the
• BCreate a separate transit gateway in every Region where the company has deployed resources.
• CCreate a virtual private gateway for the shared VPCs. Create a customer gateway for the
• DCreate VPC peering connections between the central shared VPC, the shared monitoring VPC,

• A
  6% (3)
• B
  72% (39)
• C
  7% (4)
• D
  15% (8)

Explanation

AWS Transit Gateway is regional, so you cannot directly attach VPCs from multiple Regions to a single transit gateway. The scalable, compliant design is to: - Create one transit gateway per Region. - Attach all workload VPCs and the shared directory/monitoring VPCs in that Region to the local transit gateway. - Share the transit gateways with other accounts via AWS RAM. - Peer the transit gateways across Regions and configure routes so each workload VPC can reach the central shared VPC and the shared monitoring VPC. This provides a hub-and-spoke, multi-account, multi-Region network with far less complexity than many VPC peering links or multiple VPNs, and it scales cleanly as you add more accounts or

No community discussion yet for this question.