SAP-C02 · Question #626
A software as a service (SaaS) company uses AWS to host a service that is powered by AWS PrivateLink. The service consists of proprietary software that runs on three Amazon EC2 instances behind a Netw
The correct answer is A. Configure a PrivateLink endpoint service in us-east-1 to use the existing NLB that is in eu-west-2.. Configuring a PrivateLink endpoint service in us-east-1 to use the existing NLB that is in eu- west-2 will allow the new customer to access the SaaS service without deploying new EC2 resources in us-east-1 1. Granting specific AWS accounts access to connect to the SaaS service wi
Question
A software as a service (SaaS) company uses AWS to host a service that is powered by AWS PrivateLink. The service consists of proprietary software that runs on three Amazon EC2 instances behind a Network Load Balancer (NLB). The instances are in private subnets in multiple Availability Zones in the eu-west-2 Region. All the company's customers are in eu-west- 2. However, the company now acquires a new customer in the us-east-1 Region. The company creates a new VPC and new subnets in us-east-1. The company establishes inter-Region VPC peering between the VPCs in the two Regions. The company wants to give the new customer access to the SaaS service, but the company does not want to immediately deploy new EC2 resources in us-east-1. Which solution will meet these requirements?
Options
- AConfigure a PrivateLink endpoint service in us-east-1 to use the existing NLB that is in eu-west-2.
- BCreate an NLB in us-east-1. Create an IP target group that uses the IP addresses of the
- CCreate an Application Load Balancer (ALB) in front of the EC2 instances in eu-west-2. Create an
- DUse AWS Resource Access Manager (AWS RAM) to share the EC2 instances that are in eu-
How the community answered
(48 responses)- A50% (24)
- B8% (4)
- C27% (13)
- D15% (7)
Explanation
- Configuring a PrivateLink endpoint service in us-east-1 to use the existing NLB that is in eu- west-2 will allow the new customer to access the SaaS service without deploying new EC2 resources in us-east-1 1. * Granting specific AWS accounts access to connect to the SaaS service will ensure that only authorized users can access the service 1.
Community Discussion
No community discussion yet for this question.