mediummultiple choiceObjective-mapped

A game streaming service must use UDP for real-time gameplay traffic. For external firewall allowlisting, the service requires stable, static IP addresses. The TLS handshake must be handled end-to-end by the application servers (the load balancer must not terminate TLS). Which AWS load balancing option best fits these requirements?

Question 1mediummultiple choice
Full question →

A game streaming service must use UDP for real-time gameplay traffic. For external firewall allowlisting, the service requires stable, static IP addresses. The TLS handshake must be handled end-to-end by the application servers (the load balancer must not terminate TLS). Which AWS load balancing option best fits these requirements?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Use a Network Load Balancer (NLB) with a UDP listener, configure the NLB to use Elastic IP addresses for static IPs, and use TCP listeners for TLS passthrough to the application servers.

NLB supports UDP listeners and is designed for low-latency, high-performance networking. Associating Elastic IP addresses with the NLB provides stable public IP addresses for firewall allowlisting. For TLS passthrough, using a TCP listener keeps the TLS handshake and encryption between the client and the targets (no load balancer TLS termination).

B

Distractor review

Use an Application Load Balancer (ALB) with UDP listeners and configure TLS passthrough.

ALB is intended for HTTP/HTTPS Layer 7 traffic and does not provide UDP load balancing suitable for low-latency game traffic. Even with TLS passthrough concepts, the missing UDP support makes ALB incompatible with the requirement.

C

Distractor review

Use Amazon API Gateway with a WebSocket API and keepalive pings to provide UDP-like low-latency delivery.

API Gateway WebSockets are not a replacement for UDP transport and do not provide the same semantics or latency characteristics required for real-time UDP game traffic. The requirement is specifically UDP for gameplay.

D

Distractor review

Use a Classic Load Balancer and multiplex UDP over TCP to meet the UDP and low-latency requirements.

Multiplexing UDP over TCP changes transport semantics (datagrams vs. a byte stream) and typically impacts latency and delivery characteristics. Classic ELB is also not an appropriate tool to directly satisfy UDP low-latency forwarding requirements.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Related practice questions

Related SAA-C03 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Use a Network Load Balancer (NLB) with a UDP listener, configure the NLB to use Elastic IP addresses for static IPs, and use TCP listeners for TLS passthrough to the application servers. — An NLB is the best fit because it directly supports UDP listeners for low-latency gameplay traffic. To meet static IP requirements for firewall allowlisting, configure the NLB with Elastic IP addresses. Finally, use TCP listener(s) for TLS passthrough so TLS is handled by the application servers rather than terminated at the load balancer. Why others are wrong: ALB does not provide UDP load balancing for real-time game traffic. API Gateway WebSockets operate on different protocols and do not implement UDP semantics. Classic ELB cannot directly satisfy UDP transport requirements, and multiplexing UDP over TCP changes the networking behavior and undermines the latency/transport characteristics the requirement calls for.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.