Examkin

Question

Difficulty: MediumConfigure Azure Application Gateway

An organization deploys an Azure Application Gateway v2 instance to expose two internal web applications. The applications are accessed from the internet using the URLs 'https://finance.adventureworks.com' and 'https://hr.adventureworks.com'. Both applications must use secure connections, and TLS/SSL termination must be performed at the Application Gateway. Which two configuration components should you implement on the Application Gateway to support this routing scenario?

  1. Two frontend listeners with the listener type set to Multi-site, each configured for HTTPS and associated with its respective host name and SSL certificate.Answer
  2. Two request routing rules that associate each of the multi-site listeners with their respective backend pools and HTTP settings.Answer
  3. C
    A single frontend listener of type Basic configured for HTTPS on port 443, utilizing a multi-domain SSL certificate to serve both host names.
  4. D
    An inbound Network Security Group (NSG) rule on the Application Gateway subnet that denies traffic from the GatewayManager service tag on ports 65200 through 65535.

Answer

Two frontend listeners with the listener type set to Multi-site, and two request routing rules linking each listener to its backend pool and HTTP settings.
To host multiple websites with distinct domain names on a single Application Gateway using HTTPS, you must configure multiple site-specific listeners. Multi-site listeners are required to bind each hostname (finance.adventureworks.com and hr.adventureworks.com) to its respective SSL certificate. In addition, you must create request routing rules to associate each listener with the appropriate backend pool and HTTP settings.

Step-by-Step Solution

1
Determine the type of listener required to support multiple domains on a single Application Gateway.
Identify that Multi-site listeners are required because they evaluate the Host header of incoming HTTP requests, whereas Basic listeners do not.
To route traffic to different backend pools based on whether the URL is finance.adventureworks.com or hr.adventureworks.com, the gateway must distinguish between the domains.
2
Configure the frontend listeners for TLS/SSL termination.
Create two separate HTTPS Multi-site listeners on port 443, uploading the corresponding SSL certificate and specifying the respective host name for each.
Each domain requires its own SSL certificate to secure connections, which must be terminated at the gateway's frontend listeners.
3
Configure request routing rules to forward traffic from listeners to backends.
Create two request routing rules that connect each Multi-site listener to its respective backend pool and backend HTTP settings.
Routing rules map the traffic received by a listener to the correct backend pool using the configured HTTP settings.

Key Concept

To host multiple secure websites on a single Application Gateway, you must configure separate Multi-site listeners with the correct host name bindings and certificates, and map them using request routing rules to their respective backend pools.
Rate this question

Topics

Configure Azure Application Gateway

More questions from this topic