A SysOps administrator is configuring an application on Amazon EC2 instances for a company. Teams in other countries will use the application over the internet. The company requires the application…

Question

Options

• ABehind an Amazon API Gateway API
• BBehind an Application Load Balancer
• CBehind an internet-facing Network Load Balancer
• DIn an Amazon CloudFront distribution

• A
  5% (1)
• B
  10% (2)
• C
  80% (16)
• D
  5% (1)

Explanation

An internet-facing Network Load Balancer (NLB) is the only AWS load balancing option that supports static IP addresses (one per Availability Zone) and allows you to assign Elastic IPs - making it the correct choice when clients need a predictable, unchanging IP to reach your application.

Why the others are wrong:

• A (API Gateway): Exposes an HTTPS endpoint via a hostname, not a static IP, and is designed for API management - not general application hosting.
• B (Application Load Balancer): Operates at Layer 7 and resolves only through a DNS name; its underlying IPs are dynamic and can change at any time, so it cannot guarantee a static IP.
• D (CloudFront): A CDN that serves content from distributed edge locations with no static IP - access is always via a hostname.

Memory tip: Think "NLB = Network Layer = Numbers (IPs)" - because NLB operates at Layer 4 (TCP/IP), it works directly with IP addresses and supports Elastic IP assignment, whereas ALB (Layer 7) only gives you a DNS name. Any exam question that mentions "static IP" and load balancing should immediately point you to NLB.

No community discussion yet for this question.