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?
- 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.Cevap
- Two request routing rules that associate each of the multi-site listeners with their respective backend pools and HTTP settings.Cevap
- CA single frontend listener of type Basic configured for HTTPS on port 443, utilizing a multi-domain SSL certificate to serve both host names.
- DAn inbound Network Security Group (NSG) rule on the Application Gateway subnet that denies traffic from the GatewayManager service tag on ports 65200 through 65535.
Cevap
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.
Adım Adım Çözüm
Anahtar Kavram
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.