Question 330
A Microsoft Azure administrator receives this requirement: A public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application. What is the most appropriate corrective step?
Explanation
Correct Answer
The cause is: The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. The appropriate change is: After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener. Verify it with this outcome: Controlled malicious request patterns are blocked while normal requests pass and logs record rule decisions.
Incorrect Answers
This action concerns internal app service environment isolation, where The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. The reported incident instead involves The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode.
This action concerns api management private network access, where The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. The corrective response here is “After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener”; this alternative does not provide that response.
This action concerns application gateway backend health probes, where The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. The stem reports a public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application; this control addresses a different failure condition.