Microsoft Certified: Azure Security Engineer AssociateImplement platform protectionMedium
A global company uses Azure Front Door to route traffic to its web applications deployed in various Azure regions. They need to restrict access to their web applications based on the geographic location of the client, allowing only users from specific countries to access the services. Which Azure Front Door feature should be configured to achieve this geo-filtering requirement?
- ARouting Rules
- BLoad Balancing Settings
- CHealth Probes
- DWeb Application Firewall (WAF) Geo-filtering
Show answer & explanationAnswer & explanation
Correct answer: D. Web Application Firewall (WAF) Geo-filtering
Azure Front Door's Web Application Firewall (WAF) policies include geo-filtering capabilities. This allows you to define custom rules to block or allow traffic based on the client's country/region, which is ideal for restricting access based on geographic location.
Why the other options are wrong
- A. Routing rules define how traffic is directed to backend pools, not for geo-based access restrictions.
- B. Load balancing settings configure how traffic is distributed among backend instances, not for geo-filtering.
- C. Health probes monitor the availability of backend resources, not for geographic access control.
Azure Front Door WAF Geo-filtering
Azure Front Door's Web Application Firewall (WAF) can be configured with custom rules that perform geo-filtering, allowing or blocking web traffic based on the client's country or region.
- Part of Front Door WAF policy.
- Allows defining allow/deny lists for countries/regions.
- Applies at the edge of Microsoft's network.
- Enhances security and compliance by restricting geographic access.
Memory trick: Front Door WAF Geo: Your web app's global border control.