SAP-C02 · Question #198
A large company runs workloads in VPCs that are deployed across hundreds of AWS accounts. Each VPC consists of public subnets and private subnets that span across multiple Availability Zones. NAT…
The correct answer is B. Create a transit gateway, and share it with the existing AWS accounts. Attach existing VPCs to. https://docs.aws.amazon.com/whitepapers/latest/building-scalable-secure-multi-vpc-network- infrastructure/centralized-egress-to-internet.htmlay.html
Question
A large company runs workloads in VPCs that are deployed across hundreds of AWS accounts. Each VPC consists of public subnets and private subnets that span across multiple Availability Zones. NAT gateways are deployed in the public subnets and allow outbound connectivity to the internet from the private subnets. A solutions architect is working on a hub-and-spoke design. All private subnets in the spoke VPCs must route traffic to the internet through an egress VPC. The solutions architect already has deployed a NAT gateway in an egress VPC in a central AWS account. Which set of additional steps should the solutions architect take to meet these requirements?
Options
- ACreate peering connections between the egress VPC and the spoke VPCs. Configure the
- BCreate a transit gateway, and share it with the existing AWS accounts. Attach existing VPCs to
- CCreate a transit gateway in every account. Attach the NAT gateway to the transit gateways.
- DCreate an AWS PrivateLink connection between the egress VPC and the spoke VPCs. Configure
How the community answered
(39 responses)- A13% (5)
- B62% (24)
- C21% (8)
- D5% (2)
Explanation
https://docs.aws.amazon.com/whitepapers/latest/building-scalable-secure-multi-vpc-network- infrastructure/centralized-egress-to-internet.htmlay.html
Community Discussion
No community discussion yet for this question.