AZ-700 practice question 31 of 35
You need to configure a custom rule for APPGWI-WAFPolicy to allow only connections that originate from FD1. The solution must support the planned changes. Which Match type and Match variable should you select?
Full set: 327 questionsTo restrict traffic to an Application Gateway from a specific Azure Front Door instance, the recommended and most reliable method is to use a custom Web Application Firewall (WAF) rule that filters on the X-Azure-FDID HTTP header. Azure Front Door automatically adds this header to all requests it forwards to the backend, and the header's value is the unique identifier of the Front Door instance. Therefore, the custom rule must inspect the incoming request headers. The Match variable should be RequestHeaders, and the Match type should be String to compare the value of the X-Azure-FDID header against the known ID of the FD1 instance.
A. String and RequestCookies: The unique identifier for the Front Door instance is passed in a request header, not in a cookie.
B. IP address and RemoteAddr: This method is not recommended because Front Door uses a large, shared, and dynamic set of IP ranges. This approach cannot reliably distinguish a specific Front Door instance and is difficult to maintain.
D. Geo location and RemoteAddr: This filters traffic based on the geographic location of the source IP address, which is irrelevant for identifying a specific Azure service instance like Front Door. ---
1. Microsoft Learn, Azure Front Door Documentation. "Secure traffic to Azure Application Gateway with Azure Front Door". This document explicitly details the procedure. In the section "Configure Azure Application Gateway WAF to only allow traffic from Azure Front Door," it states: "To lock down your application to accept traffic only from your specific Front Door instance, you'll need to set up a custom WAF rule in Application Gateway... This rule checks for a specific value of the X-Azure-FDID header that is sent by Azure Front Door." The configuration steps shown use RequestHeaders as the match variable and a string operator.
2. Microsoft Learn, Web Application Firewall Documentation. "Custom rules for Web Application Firewall v2 on Azure Application Gateway". In the "Match variables" section, RequestHeaders is listed as a valid variable. The document describes how to create a rule that can inspect a specific header (e.g., X-Azure-FDID) and use a string-based operator (like Contains or Equals) to match its value. This confirms that String is the correct match type for evaluating a header's value.
Keep practicing
Take the free AZ-700 practice test
Ten exam-style questions with answers and explanations, plus the exam facts and study guides.
More questions
Other AZ-700 practice questions
- Question 1You have an Azure application gateway named AppGW1 that balances requests to a web app na…
- Question 2Note: This question is part of a series of questions that present the same scenario. Each…
- Question 5You need to configure the default route on Vnet2 and Vnet3. The solution must meet the vi…
- Question 7Your company has an office in New York. The company has an Azure subscription that contai…
- Question 12Your company has 40 branch offices that are linked by using a Software-Defined Wide Area …
