AZ-700 Question 211
Select 3An online retailer hosts a global e-commerce platform in multiple Azure regions. They want to block malicious traffic at the edge, automatically direct users to the nearest healthy region to minimize latency, and serve static product images efficiently. Which three Azure Front Door features best meet these requirements? (Choose three.)
- A
Web Application Firewall (WAF) custom rules
- B
Performance-based routing
- C
Path-based routing
- D
Caching for static content
- E
URL rewriting
Show answer and explanation
Correct answers: A, B, D
Explanation
Azure Front Door offers multiple features to meet global e-commerce needs. Web Application Firewall policies help protect against harmful requests, performance-based routing ensures users are directed to the nearest healthy backend, and caching helps deliver static assets with low latency. These features collectively address the retailer� security and performance requirements. For more details, refer to Microsoft� documentation on Azure Front Door (https://learn.microsoft.com/azure/frontdoor/).
- A. Correct.
Web Application Firewall (WAF) custom rules are correct because they allow you to inspect and block malicious traffic at Azure Front Door before it reaches your application backends. This capability meets the requirement to filter dangerous traffic efficiently.
- B. Correct.
Performance-based routing is correct because it automatically directs clients to the closest available backend based on latency, thus ensuring users connect to the nearest healthy region and experience minimal response times.
- C. Incorrect.
Path-based routing is incorrect here. While useful for routing traffic to different backend pools based on URL paths, it does not address blocking malicious traffic or automatically optimizing traffic routing based on latency. It can be part of a more complex scenario, but is not the key feature for this requirement set.
- D. Correct.
Caching for static content is correct because it reduces the time needed to fetch static resources (like product images), improving response times for global users. Caching at the edge is critical for a better user experience.
- E. Incorrect.
URL rewriting is incorrect for this scenario, because rewriting the path or modifying headers does not directly help with blocking malicious traffic, nearest-backend routing, or content delivery acceleration. It's more for customizing requests rather than solving the stated requirements.