AZ-700 · Question #46
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 A. Yes. Assuming the proposed solution involved configuring a WAF exclusion, then this action would meet the goal of making the URL accessible by allowing legitimate traffic to bypass specific WAF rules.
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 disable the WAF rule that has a ruleld of 920300. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(60 responses)- A78% (47)
- B22% (13)
Why each option
Assuming the proposed solution involved configuring a WAF exclusion, then this action would meet the goal of making the URL accessible by allowing legitimate traffic to bypass specific WAF rules.
If the diagnostic logs identify a specific Web Application Firewall (WAF) rule blocking legitimate traffic, configuring a WAF exclusion list for the specific request attributes (e.g., headers, cookies, query string arguments, or request body arguments) that triggered the rule allows the traffic to bypass that WAF inspection. This effectively resolves the HTTP 403 error for legitimate requests, making the URL accessible while maintaining WAF protection for other traffic.
This choice would be incorrect because a properly configured WAF exclusion directly addresses and resolves HTTP 403 errors caused by WAF rules blocking legitimate requests.
Concept tested: Azure WAF exclusion rule configuration
Source: https://learn.microsoft.com/en-us/azure/web-application-firewall/ag/application-gateway-waf-configuration#waf-exclusion-lists
Community Discussion
No community discussion yet for this question.