You have an Azure application gateway named AppGW1 that balances requests to a web app named App1. You need to modify the server variables in the…

Azure Application Gateway's rewrite feature allows for the modification of HTTP(S) request and response headers. To modify server variables in the response header of the backend application (App1), you must configure a rewrite set. This rewrite set contains one or more rewrite rules with conditions and actions. The action would be to set, add, or delete a specific response header. This rewrite set is then associated with a routing rule to be applied to the traffic flowing through the Application Gateway to the client.

A. HTTP settings define backend properties like port, protocol, and session affinity, but they do not modify headers.

C. Rules associate listeners with backend pools and HTTP settings. While a rewrite set is applied to a rule, "rewrites" is the specific feature configured for this task.

D. Listeners are the entry point for traffic, checking for incoming requests on a specific port and protocol, but they do not perform header modifications.

1. Microsoft Learn. "Rewrite HTTP headers and URL with Azure Application Gateway." Under the "What you can rewrite" section

it explicitly states: "You can use rewrite rules in Application Gateway to add

remove

or update HTTP(S) request and response headers..."

2. Microsoft Learn. "Common rewrite scenarios in Azure Application Gateway." The document provides a specific scenario titled "Modify a response header

" which details the steps to create a rewrite rule and action to modify a response header

such as the Strict-Transport-Security header.

3. Microsoft Learn. "Application Gateway components." This document defines the purpose of each component. The "Routing rules" section explains that a rule binds a listener to a backend pool and can have a rewrite set associated with it. The "HTTP settings" section describes its role in determining protocol

port

and other settings for backend communication.