SAA-C03 · Question #784
A company runs workloads in 20 private VPCs. Each VPC has interface VPC endpoints for many AWS services. The company wants to optimize costs for its network architecture. The company must not use…
The correct answer is C. Create interface VPC endpoints and a transit gateway in a new central VPC. Use the transit. By consolidating interface VPC endpoints in a central VPC and connecting workload VPCs via a Transit Gateway, the company can reduce the number of interface endpoints in each VPC, lowering costs. This architecture allows private connectivity to AWS services without using public…
Question
A company runs workloads in 20 private VPCs. Each VPC has interface VPC endpoints for many AWS services. The company wants to optimize costs for its network architecture. The company must not use public IP addresses. Which solution will meet these requirements?
Options
- ACreate a NAT gateway in each workload VPC. Remove the interface VPC endpoints. Update the
- BReplace the interface VPC endpoints from each workload VPC with gateway endpoints. Update
- CCreate interface VPC endpoints and a transit gateway in a new central VPC. Use the transit
- DCreate gateway endpoints in a new central VPC. Use VPC peering to connect the workload VPCs
How the community answered
(52 responses)- A6% (3)
- B10% (5)
- C65% (34)
- D19% (10)
Explanation
By consolidating interface VPC endpoints in a central VPC and connecting workload VPCs via a Transit Gateway, the company can reduce the number of interface endpoints in each VPC, lowering costs. This architecture allows private connectivity to AWS services without using public IP addresses and maintains scalability across multiple VPCs.
Community Discussion
No community discussion yet for this question.