Azure Front Door Rate Limiting Configuration
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 subscription that contains an Azure Front Door Premium profile named AFD1 and an Azure Web Application Firewall (WAF) policy named WAF1. AFD1 is associated with WAF1. You need to configure a rate limit for incoming requests to AFD1. Solution: You configure a custom rule for WAF1. Does this meet the goal?
Community Votes
79% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the integration between Azure Front Door and its associated WAF policy, specifically highlighting that rate limiting is handled via WAF custom rules rather than Front Door native settings.
This question addresses how to configure rate limiting for Azure Front Door Premium. It establishes that custom rules within the associated WAF policy are the correct mechanism for this task.
Many candidates incorrectly choose 'No', believing that rate limiting must be configured directly on the Front Door profile or using Traffic Manager features, failing to recognize the WAF's role in this scenario.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Azure Front Door Premium integrates with Azure Web Application Firewall (WAF). When a WAF policy is associated with an Azure Front Door profile, you can enforce security policies, including rate limiting, by creating custom rules within that WAF policy. The official Microsoft documentation confirms that rate limiting is configured using these custom WAF rules.Why the Other Options Are Wrong
Option B ('No') is incorrect because it suggests that configuring a custom rule in WAF1 does not meet the goal. However, since AFD1 is associated with WAF1, any rule defined in WAF1 applies to traffic passing through AFD1. Therefore, the solution described in the question statement is valid and meets the requirement.Community Comment Notes
Community feedback strongly supports Option A. One user noted that "Rate limiting is configured by using custom WAF rules," referencing the official documentation. Another comment highlighted the specific documentation link for WAF Front Door custom rules, reinforcing the technical accuracy of the approach.Official Reference
Exam Strategy
When dealing with Azure Front Door Premium, always check if a WAF policy is associated. If so, remember that many security features like rate limiting and custom rules are managed within the WAF policy itself, not directly on the Front Door profile.
Frequently Asked Questions
Can I set rate limits directly on the Front Door profile without WAF?
No, rate limiting is a feature provided by Azure WAF custom rules when integrated with Front Door Premium.
Does WAF policy apply to all endpoints in Front Door?
Yes, when a WAF policy is associated with a Front Door profile, its rules apply to all backend pools and endpoints managed by that profile.
Related Analysis
Practice All AZ-700 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-700 Practice Test →