Question 940
Original unofficial Palo Alto Networks NetSec-Architect scenario: An Azure application gateway protects HTTPS ingress but inter-spoke database traffic bypasses its WAF and NGFW inspection path. Which continuing assurance practice best prevents recurrence?
Explanation
Correct Answer
Original fictional security architecture situation: An Azure application gateway protects HTTPS ingress but inter-spoke database traffic bypasses its WAF and NGFW inspection path. Governing principle: Different ingress and transit security components operate at different traffic layers and paths. The most defensible design response is: Separate layer-7 web gateway protections from the routed NGFW controls required for private east-west flows. Validation: An authorized spoke database flow passes the expected NGFW while malicious web test traffic follows the web gateway controls. Sustained assurance: Maintain a flow-to-control coverage matrix
Incorrect Answers
“Trend route growth and hub performance as branches are added.” concerns the separate design topic: architect azure ngfw insertion, load balancing and high resilience. It would not fix the described weakness: an Azure application gateway protects HTTPS ingress but inter-spoke database traffic bypasses its WAF and NGFW inspection path. Different ingress and transit security components operate at different traffic layers and paths.
This alternative is linked to the architecture category: architect aws inspection insertion, gwlb, transit gateway and ha. The actual problem is that an Azure application gateway protects HTTPS ingress but inter-spoke database traffic bypasses its WAF and NGFW inspection path; the controlling distinction is: different ingress and transit security components operate at different traffic layers and paths.
The suggested “Test failure detection before production rollout.” tests a different architectural concern: architect aws inspection insertion, gwlb, transit gateway and ha. Here, an Azure application gateway protects HTTPS ingress but inter-spoke database traffic bypasses its WAF and NGFW inspection path. Different ingress and transit security components operate at different traffic layers and paths.