Q28 — AWS SAA-C03 Ch.15

Question 28 of 100 | ← Chapter 15

Q1128. A company needs to run its external website on Amazon EC2 instances and on-premises virtualized servers. The AWS environment has a1 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?

• A. Deploy an Amazon Route 53 Resolver with rules pointing to the on-premises and AWS IP addresses.
• B. Deploy a Network Load Balancer on AWS. Create target groups for the on-premises and AWS IP addresses. ✓
• C. Deploy an Application Load Balancer on AWS.Register the on-premises and AWS IP addresses with the target group.
• D. Deploy Amazon API Gateway to direct traffic to the on-premises and AWS IP addresses based on the header of the request.

Correct Answer: B. Deploy a Network Load Balancer on AWS. Create target groups for the on-premises and AWS IP addresses.

Explanation

The best solution to meet the requirements for handling split traffic between external websites running on Amazon EC2 instances and on-premises servers, while ensuring a fixed IP address and low operational overhead, is:B. Deploy a Network Load Balancer on AWS. Create target groups for the on-premises and AWS IP addresses.Explanation:Network Load Balancer (NLB): This type of load balancer operates at the connection level (Layer 4) and can handle TCP traffic efficiently. It supports static IP addresses, which is essential for the company's requirement that some website users must allowlist specific IP addresses. Target Groups: You can configure target groups to include both the on-premises and AWS EC2 instances, allowing the NLB to distribute incoming traffic effectively while maintaining the same IP address.Why Other Options Are Not Suitable:A. Route 53 Resolver: While it can help with DNS resolution, it does not provide the necessary traffic distribution and load balancing capabilities required for managing split traffic.C. Application Load Balancer (ALB): This operates at Layer 7 and is more suited for HTTP/HTTPS traffic with advanced routing features. However, it does not natively support static IP addresses, which is a requirement in this scenario.D. Amazon API Gateway: This is designed for building APIs and would introduce additional complexity and overhead for simply directing web traffic, making it less suitable for this requirement.Thus, option B provides the most effective and low-overhead solution for managing the split traffic while meeting all specified requirements.