AZ-305 Practice Question 80: NAT Gateway SNAT Exhaustion
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 8 · question 10 of 10
A batch processing workload runs on a large virtual machine scale set behind a Standard Load Balancer. Instances make a high volume of outbound HTTPS calls to a set of external APIs, and the operations team sees intermittent outbound connection failures that correlate with SNAT port exhaustion during peak load. The design must provide a large, predictable pool of outbound SNAT ports for the subnet without redesigning the inbound load balancing configuration. What should the architect add to the virtual network?
Show answer and explanation
Answer:
A NAT gateway attached to a subnet takes over outbound internet connectivity for every resource in that subnet and provides a large, predictable SNAT port allocation: each associated public IP supplies 64,512 SNAT ports, and up to 16 public IPs can be attached for over a million ports, all without touching the existing inbound load balancer configuration.
Adding another frontend IP configuration to the load balancer changes inbound listeners, not outbound SNAT allocation, so it does not address exhaustion. Azure Firewall can provide outbound connectivity and its own SNAT, but deploying it purely to fix SNAT exhaustion for a single subnet is a much heavier and costlier redesign than attaching a NAT gateway, and it is not what the firewall is primarily positioned for here. Azure Bastion provides secure RDP and SSH access to VMs over the Azure portal; it has no role in routing or scaling general outbound internet traffic and cannot serve as a NAT device.
Reference: Troubleshoot Azure NAT Gateway connectivity