ANS-C01 · Question #127
A software-as-a-service (SaaS) company is migrating its private SaaS application to AWS. The company has hundreds of customers that connect to multiple data centers by using VPN tunnels. As the…
The correct answer is B. Use AWS PrivateLink to connect the AWS customers. Use a third-party routing appliance in the. You don't want to mess with customer's AWS VPC, whether via VPC peering or Transit gateway. The standard solution is always VPC endpoint with AWS Privatelink.
Question
A software-as-a-service (SaaS) company is migrating its private SaaS application to AWS. The company has hundreds of customers that connect to multiple data centers by using VPN tunnels. As the number of customers has grown, the company has experienced more difficulty in its effort to manage routing and segmentation of customers with complex NAT rules. After the migration to AWS is complete, the company's AWS customers must be able to access the SaaS application directly from their VPCs. Meanwhile, the company's on-premises customers still must be able to connect through IPsec encrypted tunnels. Which solution will meet these requirements?
Options
- AConnect the AWS customer VPCs to a shared transit gateway. Use AWS Site-to-Site VPN
- BUse AWS PrivateLink to connect the AWS customers. Use a third-party routing appliance in the
- CPeer each AWS customer's VPCs to the VPC that hosts the SaaS application. Create AWS Site-
- DUse Site-to-Site VPN tunnels to connect each AWS customer's VPCs to the VPC that hosts the
How the community answered
(41 responses)- A5% (2)
- B66% (27)
- C10% (4)
- D20% (8)
Explanation
You don't want to mess with customer's AWS VPC, whether via VPC peering or Transit gateway. The standard solution is always VPC endpoint with AWS Privatelink.
Topics
Community Discussion
No community discussion yet for this question.