Question 420
Following the issue — A spoke workload bypasses a hub Azure Firewall because a user-defined route points directly to the Internet. — the team takes this action: Route the spoke's eligible egress through the approved firewall next hop. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Validate effective routes after each spoke or firewall deployment. This mitigates the control weakness because: Firewall policy cannot inspect traffic that is routed around the firewall. Keep the intervention, Route the spoke's eligible egress through the approved firewall next hop., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: Azure UDR definitions affect traffic only when applied to the relevant subnet. The continuing risk here is determined by: Firewall policy cannot inspect traffic that is routed around the firewall. The targeted safeguard is “Validate effective routes after each spoke or firewall deployment”.
“Capture effective rules and routes before making security network changes” addresses a different recurring failure: Network Watcher provides complementary evidence for filtering, routing and connectivity conditions. For the condition in this question, maintain “Validate effective routes after each spoke or firewall deployment” because firewall policy cannot inspect traffic that is routed around the firewall.
That review protects the control associated with: Private Link provider-side visibility and acceptance govern who can privately connect. It does not directly prevent the stated recurrence, which concerns: Firewall policy cannot inspect traffic that is routed around the firewall. The appropriate guardrail is “Validate effective routes after each spoke or firewall deployment”.