SAA-C03 · Question #340
A company needs to run its external website on Amazon EC2 instances and on-premises virtualized servers. The AWS environment has a 1 GB AWS Direct Connect connection to the data center. The…
The correct answer is B. Deploy a Network Load Balancer on AWS. Create target groups for the on-premises and AWS IP. A Network Load Balancer (NLB) supports IP address-based targets, which allows the use of both EC2 and on-premises endpoints. It also supports a static IP address or Elastic IP, which meets the requirement for a fixed IP address needed by some users. NLB offers high performance…
Question
A company needs to run its external website on Amazon EC2 instances and on-premises virtualized servers. The AWS environment has a 1 GB AWS Direct Connect connection to the data center. The application has IP addresses that will not change. The on-premises and AWS servers are able to restart themselves while maintaining the same IP address if a failure occurs. Some website users have to add their vendors to an allow list, so the solution must have a fixed IP address. The company needs a solution with the lowest operational overhead to handle this split traffic. What should a solutions architect do to meet these requirements?
Options
- ADeploy an Amazon Route 53 Resolver with rules pointing to the on-premises and AWS IP
- BDeploy a Network Load Balancer on AWS. Create target groups for the on-premises and AWS IP
- CDeploy an Application Load Balancer on AWS. Register the on-premises and AWS IP addresses
- DDeploy Amazon API Gateway to direct traffic to the on-premises and AWS IP addresses based
How the community answered
(46 responses)- A17% (8)
- B70% (32)
- C4% (2)
- D9% (4)
Explanation
A Network Load Balancer (NLB) supports IP address-based targets, which allows the use of both EC2 and on-premises endpoints. It also supports a static IP address or Elastic IP, which meets the requirement for a fixed IP address needed by some users. NLB offers high performance, low latency, and minimal operational overhead. Application Load Balancer only supports instance or Lambda targets, not IP addresses outside the VPC. Route 53 Resolver is for DNS, and API Gateway is for HTTP-based APIs, not web applications.
Community Discussion
No community discussion yet for this question.