Question 630
VNets `vnet-app` and `vnet-data` have an established peering. An app VM in vnet-app now fails to open HTTPS on a data VM's private IP in vnet-data. Network Watcher reports the two VNet address spaces and effective VM routes as valid, and the applicable NSGs already allow TCP/443. Inspection shows `allowVirtualNetworkAccess = false` on the vnet-app-to-vnet-data peering, while the reverse peering permits virtual network access. Neither VNet uses a gateway or transit NVA for this private flow. What change addresses the observed block?
Explanation
Correct Answer
Allow virtual network access controls whether VM traffic from this peered VNet can reach VM IPs in the remote peered address space. It is explicitly disabled on the source peering, so enabling it restores that prerequisite, subject to the already validated reverse setting, routing and NSG controls.
Incorrect Answers
Allow forwarded traffic concerns packets forwarded into the peering by a network virtual appliance and does not replace disabled direct VNet access. The app VM is the original sender, not an NVA forwarding someone else's traffic.
Gateway transit concerns using a gateway in a remote peered VNet. No gateway is involved in this direct east-west connection, and this flag does not override `allowVirtualNetworkAccess = false`.
A route to a nonexistent VPN gateway is not a valid repair. The effective VNet peering route is already present; only the peering's disabled virtual network access permission is implicated.