A company hosts an application on Amazon EC2 instances behind an Application Load Balancer (ALB). One of the company's vendors needs a static IP address. The vendor will add this static IP address…

Question

Options

• AAssociate an Elastic IP address with the ALB.
• BAssociate an AWS WAF web ACL that has an IP match condition rule with the ALB.
• CCreate a VPC endpoint. Associate the VPC endpoint with the ALB.
• DReplace the ALB with a Network Load Balancer.

• A
  8% (3)
• B
  3% (1)
• C
  16% (6)
• D
  73% (27)

Explanation

Network Load Balancers (NLBs) support static IP addresses - one per Availability Zone - which can be assigned as Elastic IP addresses, making NLBs the right fit when a vendor needs a fixed IP to allowlist. Option A is wrong because ALBs do not support Elastic IP association; their IPs are dynamic and managed by AWS. Option B is wrong because AWS WAF web ACLs filter incoming traffic based on rules - they have nothing to do with assigning static outbound IPs. Option C is wrong because VPC endpoints are used to privately connect your VPC to AWS services, not to assign static IPs to load balancers.

Memory tip: Think "NLB = Network = fixed IP" - Network Load Balancers operate at Layer 4 and support static/Elastic IPs, while Application Load Balancers operate at Layer 7 and sacrifice static IPs for advanced HTTP routing features. Whenever a question mentions a vendor needing to allowlist a static IP, that's your signal to reach for NLB.

No community discussion yet for this question.