Question 370
During a cloud security review, the operations team observes: A spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet. What should the engineer implement first to address the weakness?
Explanation
Correct Answer
The cause is: Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The appropriate change is: Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints. Verify it with this outcome: A spoke workload reaches the on-premises network via the shared hub gateway without deploying a second gateway.
Incorrect Answers
This action concerns overlapping vnet address spaces, where Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. The reported incident instead involves Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.
This action concerns azure firewall application rule fqdn filtering, where A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. The corrective response here is “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints”; this alternative does not provide that response.
This action concerns vnet peering non transitivity, where VNet peering does not inherently create transitive routing between other independently peered VNets. The stem reports a spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet; this control addresses a different failure condition.