AZ-700 · Question #48
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. Assuming the proposed solution was to perform an action unrelated to WAF rule configuration (e.g., restarting the Application Gateway), then this action would not resolve an HTTP 403 error caused by a Web Application Firewall (WAF) rule.
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure application gateway that has Azure Web Application Firewall (WAF) enabled. You configure the application gateway to direct traffic to the URL of the application gateway. You attempt to access the URL and receive an HTTP 403 error. You view the diagnostics log and discover the following error. You need to ensure that the URL is accessible through the application gateway. Solution: You create a WAF policy exclusion request headers that contain 137.135.10.24. Does this meet the goat?
Options
- AYes
- BNo
How the community answered
(41 responses)- A17% (7)
- B83% (34)
Why each option
Assuming the proposed solution was to perform an action unrelated to WAF rule configuration (e.g., restarting the Application Gateway), then this action would not resolve an HTTP 403 error caused by a Web Application Firewall (WAF) rule.
This choice would be incorrect because an action like a simple restart or unrelated configuration change does not modify the active WAF rule set or its evaluation logic, thus it would not resolve a WAF-induced HTTP 403 error.
If the proposed solution does not directly address the WAF rule causing the HTTP 403 error, such as restarting the Application Gateway or modifying irrelevant backend settings, then the WAF will continue to block the traffic. An HTTP 403 from WAF requires specific WAF configuration changes, like adding an exclusion or disabling a rule, rather than general gateway management actions.
Concept tested: Azure WAF troubleshooting principles and ineffective actions
Source: https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/troubleshoot-waf-v2-application-gateway
Community Discussion
No community discussion yet for this question.