A utilities API needs only TCP load balancing without HTTP routing, WAF integration, or path-based rules. How should the architect choose a load balancer with cost in mind?
Select an answer to reveal the explanation.
Short Explanation
Don't buy the Swiss-army ALB when all you need is a TCP crowbar. Match ALB vs NLB to the features you actually use—Layer-4 TCP leans NLB; fancy HTTP routing earns the ALB.
Full Explanation
Load balancer choice should follow required features and cost. NLB excels at high-performance Layer-4 TCP/UDP; ALB provides Layer-7 HTTP(S) routing, WAF integration, and related features. Paying for unused ALB capabilities when only TCP is required is wasteful; likewise, forcing NLB when path-based HTTP rules are needed is a poor fit. API Gateway and Global Accelerator solve different problems.