AZ-305 ยท Internet connectivity and load balancing
Public IPs, NAT Gateway and Bastion
Public IP SKUs, NAT Gateway for outbound SNAT, Azure Bastion for admin access without public IPs, avoiding public IPs on VMs.
Key points
- Public IP Standard: static, closed inbound until an NSG allows, zonal or zone-redundant; Basic retired.
- NAT Gateway: subnet SNAT, no unsolicited inbound, 16 IPs max; StandardV2 zone-redundant.
- Beats instance IPs and LB outbound rules; loses only to a 0.0.0.0/0 UDR.
- New VNets from 31 March 2026: private subnets, no default outbound.
- Bastion: RDP/SSH without public IPs; AzureBastionSubnet /26+; Premium: session recording.
Source: https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview
Practice questions
What does an Azure NAT Gateway attached to a subnet provide?
- Inbound port forwarding from the internet to the subnet's VMs
- Outbound internet connectivity through its public IPs, with no unsolicited inbound
- Layer 4 load balancing of inbound flows across the subnet
- Browser-based RDP and SSH access to the subnet's VMs
Show answer
Answer: B. Outbound internet connectivity through its public IPs, with no unsolicited inbound
A NAT gateway gives every resource in the subnet outbound internet access through its static public IPs; only replies to those outbound flows come back in. It does not accept new inbound connections, balance load, or provide admin access.
Which statements describe a Standard SKU (v1) public IP address?
- It always uses static allocation
- Inbound traffic is blocked until a network security group allows it
- It can be created as zonal or zone-redundant
- It can be allocated dynamically to save cost
- It can be attached to a StandardV2 NAT gateway
Show answer
Answer: A. It always uses static allocation, B. Inbound traffic is blocked until a network security group allows it, C. It can be created as zonal or zone-redundant
Standard public IPs are static only, are closed to inbound traffic until an NSG allows it, and can be zonal or zone-redundant. Dynamic allocation belonged to the retired Basic SKU, and a StandardV2 NAT gateway accepts only StandardV2 public IPs.
If a VM has its own instance-level public IP and its subnet also has a NAT gateway, new outbound connections from the VM leave through the VM's own public IP.
Show answer
Answer: False
False. For new connections the NAT gateway takes precedence over instance-level public IPs and load balancer outbound rules; only a UDR that sends 0.0.0.0/0 to an NVA or virtual network gateway overrides it. The VM's own public IP still accepts inbound traffic.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
