Question

Difficulty: EasyConfigure Azure Application Gateway

Your organization is planning to deploy an Azure Application Gateway to load balance traffic across multiple backend web servers. You need to prepare the environment and configure the gateway. Organize the configuration steps in the correct sequential order from start to finish.

  1. 1Create a dedicated subnet within the virtual network.
  2. 2Deploy the Azure Application Gateway instance and configure its frontend IP address.
  3. 3Define the backend pool containing the target web servers.
  4. 4Configure a routing rule to link the frontend listener to the backend pool using HTTP settings.

Answer

The correct sequence of steps to configure the Application Gateway is: first, create a dedicated subnet; second, deploy the gateway instance and its frontend IP; third, define the backend pool; and fourth, configure the routing rule to link the listener to the backend pool.
The correct sequence starts with preparing the network environment by creating a dedicated subnet. Once the network is ready, the Application Gateway resource is provisioned with a frontend IP. Next, the backend pool must be defined to establish the destination targets. Finally, the routing rule is created to link the listener (frontend) to the backend pool (backend).

Step-by-Step Solution

1
Create a dedicated subnet.
An empty subnet is successfully created in the virtual network.
Azure Application Gateway must reside in its own dedicated subnet that contains no other resources.
2
Deploy the Application Gateway and configure the frontend IP.
The Application Gateway instance is provisioned and associated with a public or private IP address.
This sets up the gateway resource and defines the IP address where clients will connect.
3
Configure the backend pool.
A backend pool is created and populated with target virtual machines, scale sets, or IP addresses.
The backend pool defines the destination web servers that will process the incoming requests.
4
Create the routing rule.
A routing rule binds the frontend listener to the backend pool using backend HTTP settings.
This finalizes the configuration by linking the incoming traffic listener to the target backend servers.

Key Concept

Azure Application Gateway deployment workflow
Estimated Time:1m 0s
Rate this question