Question 620
HubNet is peered to SpokeA and SpokeB; the spokes have no direct peering or hub forwarding configuration. Why is SpokeA unable to reach SpokeB privately by default?
Explanation
Correct Answer
A hub-spoke design needs an explicit transit path because two separate peering relationships do not automatically create spoke-to-spoke forwarding.
Incorrect Answers
Overlapping prefixes make route selection ambiguous and do not enable transit.
Azure peering is not transitive by default; hub forwarding and route configuration are separate.
Public VM IP addresses are not required to route private traffic via a supported NVA.