Question 770
An Azure security engineer investigates the following incident: A security team deploys a WAF at Azure Front Door but clients can bypass all filtering by requesting the publicly reachable origin hostname directly. Which outcome most clearly verifies that the issue is resolved?
Explanation
Correct Answer
This validates the specific control for front door origin bypass mitigation: The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. The associated corrective action is: Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable. Testing a different component would not establish this result.
Incorrect Answers
An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. “Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources” would address that alternative cause, not the condition in this question: the origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path.
“Configure relevant firewall diagnostic categories and secure retention for rule and threat events” responds to this separate finding: required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. This question instead needs “Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable”, so the alternative does not meet the stated condition.
The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. “Run Network Watcher IP flow verify with the test source, destination, direction and port” applies to that separate problem. The observed case is a security team deploys a WAF at Azure Front Door but clients can bypass all filtering by requesting the publicly reachable origin hostname directly; choosing this alternative would address the wrong failure mode.