A retailer hosts a public web application on Azure App Service behind Azure Front Door and must design protection against common web exploits such as SQL injection and cross-site scripting, with managed rule sets that update as new exploits emerge. Which capability should the architect specify at the edge to meet this web workload requirement?
- AAzure DDoS Protection on the Front Door profile, inspecting application requests against managed rule sets to block SQL injection and cross-site scripting attempts before they reach the App Service origin.
- BNetwork security groups on the App Service subnet, inspecting application requests against managed rule sets to block SQL injection and cross-site scripting attempts before they reach the origin.
- CAzure Web Application Firewall on Azure Front Door, inspecting application requests against managed rule sets to block SQL injection and cross-site scripting attempts before they reach the App Service origin. Correct
- DMicrosoft Defender for App Service, inspecting application requests against managed rule sets to block SQL injection and cross-site scripting attempts before they reach the App Service origin.
Why A is wrong: DDoS Protection is tempting because it shields the public endpoint, but it defends availability against volumetric and protocol floods at the network layer and does not inspect application payloads for injection or scripting exploits.
Why B is wrong: Network security groups appeal as a filtering control, but they allow or deny traffic by IP address, port, and protocol and cannot parse HTTP payloads to detect injection or cross-site scripting exploits.
Why C is correct: The Azure Web Application Firewall on Front Door applies managed OWASP rule sets that are updated as exploits emerge and blocks injection and scripting attacks inline at the edge, which is exactly the web workload protection the requirement specifies.
Why D is wrong: Defender for App Service is tempting because it protects the same workload, but it detects threats and surfaces alerts on the running app rather than inline-blocking malicious web requests at the edge with managed rule sets.