Hotspot Question You have an Azure subscription that contains the application gateways shown in the following table. You need to configure settings to implement URL rewrite and prevent SQL injection…

Question

Exhibit

Answer Area

• Implement URL rewrite:
  GW2 onlyGW3 onlyGW1 and GW2 onlyGW2 and GW3 onlyGW1, GW2, and GW3
• Prevent SQL injection attacks:
  GW2 onlyGW3 onlyGW1 and GW2 onlyGW2 and GW3 onlyGW1, GW2, and GW3

Explanation

This question tests knowledge of Azure Application Gateway SKU tiers and which features are supported by each tier. Specifically, it evaluates understanding of URL Rewrite and WAF (Web Application Firewall) SQL injection prevention capabilities across Standard, Standard_v2, WAF, and WAF_v2 SKUs.

Approach. URL Rewrite is only supported on the v2 SKUs (Standard_v2 and WAF_v2), not on the original v1 SKUs (Standard and WAF). SQL injection prevention via WAF is only available on WAF-enabled SKUs (WAF and WAF_v2), not on Standard or Standard_v2. Therefore, to implement URL Rewrite, you need Standard_v2 or WAF_v2. To prevent SQL injection attacks using WAF rules (OWASP CRS), you need WAF or WAF_v2. Only WAF_v2 supports BOTH features simultaneously, making it the most feature-rich tier. When the table presents gateways with specific SKUs, match each requirement: URL Rewrite → any v2-tier gateway (Standard_v2 or WAF_v2); SQL Injection Prevention → any WAF-tier gateway (WAF v1 or WAF_v2).

Concept tested. Azure Application Gateway SKU tier feature compatibility - specifically which tiers support URL Rewrite (v2 SKUs only) versus WAF-based SQL injection prevention (WAF SKUs only), and understanding that WAF_v2 is the only SKU supporting both features.

Reference. https://docs.microsoft.com/en-us/azure/application-gateway/rewrite-http-headers-url and https://docs.microsoft.com/en-us/azure/application-gateway/features

No community discussion yet for this question.