You have a web app named WebApp1. You create a web application firewall (WAF) policy named WAF1. You need to protect WebApp1 by using WAF1. What should you do first?

Question

Options

• ADeploy an Azure Front Door.
• BAdd an extension to WebApp1.
• CDeploy Azure Firewall.

• A
  77% (27)
• B
  6% (2)
• C
  17% (6)

Explanation

Explanation

Deploying an Azure Front Door is the required first step because WAF policies in Azure must be associated with a supported gateway service - either Azure Front Door or Azure Application Gateway - before they can be linked to a web application. Without a Front Door (or Application Gateway) instance acting as the entry point, there is no mechanism to apply the WAF policy to WebApp1's incoming traffic.

Option B is incorrect because adding an extension to WebApp1 is not how WAF protection is implemented in Azure; WAF operates at the network/application delivery layer, not as a server-side extension. Option C is incorrect because Azure Firewall is a network-level firewall designed for general traffic filtering (Layers 3–7 for network rules), and it does not support WAF policies, which are specifically designed for HTTP/HTTPS web application protection.

Memory Tip: Think of Azure Front Door as the "front gate" of your web app - WAF is the security guard, but the guard needs a gate to stand at. No Front Door = nowhere to attach the WAF policy.

No community discussion yet for this question.