Question 260
Following the issue — A hub-and-spoke design allows every spoke to peer with the hub but assumes spokes can route through the hub automatically. — the team takes this action: Configure supported hub routing and forwarding using the intended network appliance or gateway. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Test routing transitivity explicitly rather than inferring it from peering status. This mitigates the control weakness because: VNet peering is not intrinsically transitive between independent spokes. Keep the intervention, Configure supported hub routing and forwarding using the intended network appliance or gateway., in the approved deployment, monitoring and change governance process.
Incorrect Answers
That review protects the control associated with: Managed PaaS network integration may require protected service traffic paths independent of application routes. It does not directly prevent the stated recurrence, which concerns: VNet peering is not intrinsically transitive between independent spokes. The appropriate guardrail is “Test routing transitivity explicitly rather than inferring it from peering status”.
This safeguard is for the dependency described by: Frontend TLS termination does not automatically encrypt every backend hop. The continuing risk here is determined by: VNet peering is not intrinsically transitive between independent spokes. The targeted safeguard is “Test routing transitivity explicitly rather than inferring it from peering status”.
“Audit firewall policy assignment drift across subscriptions” addresses a different recurring failure: Central Firewall Manager policy management depends on correct policy assignment and inheritance. For the condition in this question, maintain “Test routing transitivity explicitly rather than inferring it from peering status” because vNet peering is not intrinsically transitive between independent spokes.