ANS-C01 Question 73
Select 1An organization is deploying a web application on AWS that will be accessed by users from the internet. The application also requires an internal API to communicate with a database and other services within a private subnet. The organization wants to ensure secure and efficient traffic distribution for both internet-facing and internal communication. Which combination of load balancers should they use to meet these requirements?
- A
An Application Load Balancer (ALB) for the internet-facing traffic and a Network Load Balancer (NLB) for internal API communication.
- B
An Application Load Balancer (ALB) for the internet-facing traffic and an internal-facing Application Load Balancer (ALB) for internal API communication.
- C
A Network Load Balancer (NLB) for the internet-facing traffic and an Application Load Balancer (ALB) for internal API communication.
- D
Only a single internet-facing Application Load Balancer (ALB) for both internet-facing traffic and internal API communication.
Show answer and explanation
Correct answer: B
Explanation
To meet the requirements of an internet-facing web application and internal API communication, the organization should use an internet-facing Application Load Balancer (ALB) to handle external user requests and an internal-facing ALB to manage internal API communication. ALBs operate at Layer 7 and provide advanced routing features, making them suitable for both use cases while maintaining traffic separation and security.
- A. Incorrect.
An ALB for internet-facing traffic and an NLB for internal communication is not the best choice because an NLB is typically used for high-performance, low-latency use cases rather than application-layer routing, which is needed for the API communication.
- B. Correct.
An ALB for internet-facing traffic and an internal-facing ALB for internal API communication is the correct choice because the ALB provides advanced application-layer routing and security features for both external and internal traffic while maintaining separation of traffic flows.
- C. Incorrect.
An NLB for internet-facing traffic is not ideal since the application likely requires application-layer routing, which is not supported by an NLB. ALBs are better suited for HTTP/HTTPS traffic.
- D. Incorrect.
Using a single ALB for both internet-facing and internal API communication is not recommended because it does not separate the external and internal traffic, potentially exposing internal services to unnecessary risks.