Soru

Zorluk: Çok zorConfigure Azure Application Gateway

An administrator is deploying an Azure Application Gateway v2 to load balance traffic for two secure web applications, `app1.contoso.com` and `app2.contoso.com`, which are hosted on virtual machines in a separate peered virtual network named `VNet-Backend`.

You must meet the following requirements:
- Incoming traffic to `https://app1.contoso.com/images/*` must be routed to a backend pool named `ImagePool`.
- All other traffic to `https://app1.contoso.com/*` must be routed to a backend pool named `App1Pool`.
- Incoming traffic to `https://app2.contoso.com/*` must be routed to a backend pool named `App2Pool`.
- HTTPS connections must be decrypted at the Application Gateway (SSL termination).
- The Application Gateway must be able to communicate with the Azure infrastructure and route traffic to the peered backend VMs.

Which configuration should you implement to satisfy these requirements?

  1. Configure two multi-site HTTPS listeners on port 443 (one for `app1.contoso.com` and one for `app2.contoso.com`), each with its own SSL certificate. Associate a path-based routing rule with the listener for `app1.contoso.com` to map `/images/*` to `ImagePool` and the default path to `App1Pool`. Associate a basic routing rule with the listener for `app2.contoso.com` to route traffic to `App2Pool`. Ensure the gateway subnet Network Security Group (NSG) allows inbound traffic on ports 65200-65535 from the `GatewayManager` service tag, and verify no User-Defined Route (UDR) redirects internet-bound traffic (0.0.0.0/00.0.0.0/0) to a virtual appliance.Cevap
  2. B
    Configure two multi-site HTTPS listeners on port 443 (one for `app1.contoso.com` and one for `app2.contoso.com`), each with its own SSL certificate. Associate a path-based routing rule with the listener for `app1.contoso.com` to map `/images/*` to `ImagePool` and the default path to `App1Pool`. Associate a basic routing rule with the listener for `app2.contoso.com` to route traffic to `App2Pool`. Apply an Network Security Group (NSG) to the gateway subnet with a custom rule that denies all inbound traffic with a priority of 100 to secure the gateway from unauthorized public access.
  3. C
    Configure two multi-site HTTPS listeners on port 443 (one for `app1.contoso.com` and one for `app2.contoso.com`), each with its own SSL certificate. Associate a path-based routing rule with the listener for `app1.contoso.com` to map `/images/*` to `ImagePool` and the default path to `App1Pool`. Associate a basic routing rule with the listener for `app2.contoso.com` to route traffic to `App2Pool`. Associate a route table to the gateway subnet containing a default route (0.0.0.0/00.0.0.0/0) with a next hop type of Virtual Appliance pointing to an Azure Firewall.
  4. D
    Configure a single basic HTTPS listener on port 443 with a wildcard certificate. Create a path-based routing rule that maps path `/images/*` to `ImagePool`, `/app1/*` to `App1Pool`, and `/app2/*` to `App2Pool`. Rely on virtual network peering to allow the Application Gateway to route traffic to the backend VMs in `VNet-Backend` through a non-peered intermediate transit virtual network.

Cevap

Configure two multi-site HTTPS listeners on port 443, one path-based routing rule for the domain requiring path routing, one basic routing rule for the domain with a single backend pool, and ensure the gateway subnet NSG and UDR are configured to allow Azure infrastructure management communication.
The correct configuration uses multi-site HTTPS listeners on port 443 to distinguish between incoming requests for the distinct domain names. It maps `app1.contoso.com` to a path-based routing rule to handle path-based redirection, and `app2.contoso.com` to a basic routing rule. It also respects the subnet constraints of Application Gateway v2 by allowing inbound `GatewayManager` traffic on ports 65200-65535 and avoiding forced tunneling of outbound traffic via UDRs.

Adım Adım Çözüm

1
Determine the listener type.
Two multi-site listeners are required.
Since the gateway must route traffic for two distinct host headers (`app1.contoso.com` and `app2.contoso.com`) over the same port (443), basic listeners cannot be used; multi-site listeners must be configured to process host headers.
2
Configure the routing rules.
One path-based routing rule and one basic routing rule are configured.
Traffic to `app1.contoso.com` requires routing based on the URL path `/images/*` (path-based routing rule), while traffic to `app2.contoso.com` is sent entirely to `App2Pool` regardless of the path (basic routing rule).
3
Configure the gateway subnet NSG rules.
Allow inbound traffic on ports 65200-65535 from the `GatewayManager` service tag.
Application Gateway v2 requires these ports to be open for backend health monitoring and management by the Azure infrastructure. Blocking this traffic prevents the gateway from operating.
4
Configure gateway subnet routing rules.
Do not redirect default route (0.0.0.0/00.0.0.0/0) to a virtual appliance.
Direct internet connectivity is mandatory for the management and control plane of Application Gateway v2. Forcing internet traffic to a virtual appliance (forced tunneling) is not supported and will break gateway management.

Anahtar Kavram

Azure Application Gateway Listener Types, Routing Rules, and Subnet Requirements
Bu soruyu puanla