Question 670
A route-based Azure VPN Gateway `VpnGw2` connects an Azure VNet `10.0.1.0/24` to a branch network that independently also uses `10.0.1.0/24`. The supported IPsec connection is established, but route matching cannot distinguish the two address spaces. The organization cannot renumber either network and has reserved distinct unused translated /24 ranges for both sides. Which gateway configuration resolves the overlap on that connection?
Explanation
Correct Answer
Azure VPN Gateway NAT supports route-based IPsec cross-premises connections on VpnGw2 and compatible SKUs. For overlap between the VNet and branch, ingress and egress SNAT use separate nonconflicting external mappings; link the rules to the intended connection and check translated routes or BGP settings as appropriate.
Incorrect Answers
IngressSNAT maps the on-premises side into an unambiguous translated range. With the Azure VNet still using the same original prefix on that connection, the scenario continues to contain an overlapping local-versus-remote network space requiring separate egress mapping.
EgressSNAT gives the Azure VNet a translated representation for the branch, but on-premises traffic still advertises the identical unmodified prefix. Because both sides use the same original /24, Microsoft documents configuring both sides' translation on that VPN connection.
BGP route translation advertises already configured post-NAT prefixes as applicable. Without the underlying NAT mapping rules it does not translate packet addresses or solve the overlapping 10.0.1.0/24 endpoint prefixes.