WAF with Application Gateway in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to enable the Web Application Firewall (WAF) on the Application Gateway.

Azure

az network application-gateway waf-config set --gateway-name myAppGateway --resource-group myResourceGroup --[1] Enabled

Drag options to blanks, or click blank then click option'

Afirewall-mode

Bwaf-policy

Cwaf-mode

Dwaf-enabled

Attempts:

3 left

💡 Hint

Common Mistakes

Using --firewall-mode instead of --waf-enabled

Using --waf-policy which is for policies, not enabling WAF

The correct parameter to enable WAF on the Application Gateway is --waf-enabled.

2fill in blank

medium

Complete the code to create a WAF policy with prevention mode.

Azure

az network application-gateway waf-policy create --name myWafPolicy --resource-group myResourceGroup --mode [1]

Drag options to blanks, or click blank then click option'

APrevention

BDetection

CMonitor

DBlock

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Detection' mode which only logs threats

Using 'Block' which is not a valid mode

The WAF policy mode to actively block threats is Prevention.

3fill in blank

hard

Fix the error in the command to associate the WAF policy with the Application Gateway.

Azure

az network application-gateway update --name myAppGateway --resource-group myResourceGroup --[1] myWafPolicy

Drag options to blanks, or click blank then click option'

Awaf-policy

Bwaf-policy-id

Cwaf-policy-name

Dwaf-policy-resource

Attempts:

3 left

💡 Hint

Common Mistakes

Using --waf-policy with just the policy name

Using incorrect parameter names

The correct parameter to associate a WAF policy is --waf-policy-id, which requires the full resource ID.

4fill in blank

hard

Fill both blanks to configure custom rules in the WAF policy.

Azure

az network application-gateway waf-policy custom-rule create --policy-name myWafPolicy --resource-group myResourceGroup --name myRule --priority [1] --action [2] --rule-type MatchRule

Drag options to blanks, or click blank then click option'

A100

BAllow

CBlock

D200

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-numeric priority

Using 'Allow' when the rule should block

The priority should be a number like 100, and the action to block requests is Block.

5fill in blank

hard

Fill all three blanks to create a match condition for the custom WAF rule.

Azure

az network application-gateway waf-policy custom-rule condition create --policy-name myWafPolicy --resource-group myResourceGroup --rule-name myRule --match-variables [1] --operator [2] --match-values [3]

Drag options to blanks, or click blank then click option'

ARequestHeaders

BContains

CUser-Agent

DEquals

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Equals' when 'Contains' is needed

Using incorrect match variable

The match variable is RequestHeaders, the operator is Contains, and the match value is User-Agent header.

Practice

1. What is the main purpose of enabling WAF (Web Application Firewall) on an Azure Application Gateway?

easy

A. To provide a database backup solution

B. To protect web applications from common web attacks like SQL injection and cross-site scripting

C. To increase the speed of the web application by caching content

D. To monitor network traffic at the virtual network level

Solution

1. Step 1: Understand WAF's role

   WAF is designed to protect web apps by filtering and monitoring HTTP traffic to block common attacks.

2. Step 2: Compare options

   Only To protect web applications from common web attacks like SQL injection and cross-site scripting describes protection from web attacks, which is the core function of WAF.

3. Final Answer:

   To protect web applications from common web attacks like SQL injection and cross-site scripting -> Option B

4. Quick Check:

   WAF protects web apps = C [OK]

Hint: WAF blocks web attacks, not speeds or backups [OK]

Common Mistakes:

• Confusing WAF with caching or backup services
• Thinking WAF monitors network traffic broadly
• Assuming WAF improves app speed

2. Which of the following is the correct way to enable WAF on an Azure Application Gateway using ARM template syntax?

easy

A. "sku": { "name": "WAF_v2" }, "wafConfiguration": { "enabled": true, "firewallMode": "Prevention" }

B. "sku": { "name": "Standard_v2" }, "wafConfiguration": { "enabled": true }

C. "sku": { "name": "Basic" }, "wafConfiguration": { "enabled": false }

D. "sku": { "name": "WAF_v1" }, "wafConfiguration": { "enabled": false, "firewallMode": "Detection" }

Solution

1. Step 1: Identify correct SKU for WAF

   WAF requires SKU like "WAF_v2" or "WAF_v1"; Standard_v2 or Basic do not enable WAF.

2. Step 2: Check WAF configuration

   WAF must be enabled with "enabled": true and a valid firewallMode like "Prevention" or "Detection".

3. Final Answer:

   "sku": { "name": "WAF_v2" }, "wafConfiguration": { "enabled": true, "firewallMode": "Prevention" } -> Option A

4. Quick Check:

   WAF SKU + enabled true + mode = A [OK]

Hint: WAF needs WAF SKU and enabled true [OK]

Common Mistakes:

• Using Standard or Basic SKU without WAF
• Setting enabled to false when enabling WAF
• Omitting firewallMode or using invalid values

3. Given this snippet of ARM template for Application Gateway WAF configuration:

{
  "sku": { "name": "WAF_v2" },
  "wafConfiguration": {
    "enabled": true,
    "firewallMode": "Detection"
  }
}

What will be the behavior of the Application Gateway regarding detected threats?

medium

A. It will log detected threats but allow traffic to pass through

B. It will block detected threats and return an error to clients

C. It will ignore detected threats and not log them

D. It will shut down the Application Gateway on threat detection

Solution

1. Step 1: Understand firewallMode 'Detection'

   Detection mode means WAF monitors and logs threats but does not block traffic.

2. Step 2: Compare options with behavior

   Only It will log detected threats but allow traffic to pass through matches detection mode behavior: logging threats but allowing traffic.

3. Final Answer:

   It will log detected threats but allow traffic to pass through -> Option A

4. Quick Check:

   Detection mode = log only, no block = B [OK]

Hint: Detection mode logs but does not block [OK]

Common Mistakes:

• Confusing Detection with Prevention mode
• Assuming threats are blocked in Detection mode
• Thinking Application Gateway shuts down on threats

4. You configured WAF on Application Gateway with this snippet:

{
  "sku": { "name": "WAF_v2" },
  "wafConfiguration": {
    "enabled": true,
    "firewallMode": "Prevention"
  }
}

But the WAF is not blocking malicious requests. What is the most likely cause?

medium

A. The Application Gateway is missing a listener configuration

B. The SKU name "WAF_v2" does not support prevention mode

C. The WAF policy is not associated with the Application Gateway

D. The firewallMode should be set to Detection to block requests

Solution

1. Step 1: Check WAF policy association

   Even if WAF is enabled, it must have a WAF policy linked to enforce rules and block threats.

2. Step 2: Validate other options

   Listener is required but unrelated to blocking; prevention mode blocks; WAF_v2 supports prevention mode.

3. Final Answer:

   The WAF policy is not associated with the Application Gateway -> Option C

4. Quick Check:

   WAF policy association needed to block = D [OK]

Hint: WAF needs policy linked to block threats [OK]

Common Mistakes:

• Confusing detection and prevention modes
• Forgetting to associate WAF policy
• Assuming SKU limits prevention mode

5. You want to protect your web app with Azure Application Gateway WAF in prevention mode but also need to monitor false positives before blocking. What is the best approach to achieve this?

hard

A. Use Basic SKU Application Gateway with WAF enabled

B. Enable WAF in prevention mode immediately and block all detected threats

C. Disable WAF and rely on network security groups for protection

D. Enable WAF in detection mode first, review logs, then switch to prevention mode

Solution

1. Step 1: Understand prevention vs detection modes

   Prevention mode blocks threats immediately; detection mode only logs them for review.

2. Step 2: Plan safe deployment

   Start with detection mode to identify false positives, then switch to prevention to block real threats safely.

3. Final Answer:

   Enable WAF in detection mode first, review logs, then switch to prevention mode -> Option D

4. Quick Check:

   Detect first, then prevent = A [OK]

Hint: Detect first, then switch to prevention mode [OK]

Common Mistakes:

• Blocking immediately without monitoring false positives
• Disabling WAF and relying on unrelated protections
• Using Basic SKU which does not support WAF