Soru

Zorluk: Çok zorConfigure Azure Application Gateway

An administrator is deploying an Azure Application Gateway v2 (Standard_v2 SKU) in Subnet-GW within VNet-Hub to host two secure websites: partners.contoso.com and internal.contoso.com. Both sites must share the same public IP address on the gateway. The configuration requirements are:

1. partners.contoso.com requires end-to-end SSL encryption. The backend pool contains virtual machines in VNet-Spoke1 (peered to VNet-Hub) defined by FQDNs registered in a private DNS zone named private.contoso.com. These virtual machines use self-signed certificates.
2. internal.contoso.com requires SSL termination at the gateway. The backend pool consists of Azure App Service instances. Requests to internal.contoso.com/images/* must be routed to an Azure Storage account static website.
3. The gateway subnet must be secured using a Network Security Group (NSG) and allow management traffic.

Which of the following configurations must be implemented to meet these requirements?

  1. A
    Configure two multi-site HTTPS listeners: one for partners.contoso.com and one for internal.contoso.com. For partners.contoso.com, create a basic routing rule to the VM backend pool, set the backend protocol to HTTPS, upload the self-signed certificate (.cer) as a Trusted Root Certificate, and link VNet-Spoke1 to the private.contoso.com private DNS zone while leaving VNet-Hub unlinked. For internal.contoso.com, create a path-based routing rule with a default target pointing to the App Service backend pool, set the backend protocol to HTTP, enable host header override in the HTTP settings, and define a path map for /images/* pointing to the storage account backend pool. Apply an NSG to Subnet-GW with an inbound rule allowing GatewayManager traffic on ports 6520065200-6553565535 at priority 100100.
  2. B
    Configure two multi-site HTTPS listeners: one for partners.contoso.com and one for internal.contoso.com. For partners.contoso.com, create a basic routing rule to the VM backend pool, set the backend protocol to HTTPS, upload the self-signed certificate (.cer) as a Trusted Root Certificate, and link VNet-Hub to the private.contoso.com private DNS zone. For internal.contoso.com, create a path-based routing rule with a default target pointing to the App Service backend pool, set the backend protocol to HTTP, enable host header override in the HTTP settings, and define a path map for /images/* pointing to the storage account backend pool. Configure a User-Defined Route (UDR) in Subnet-GW for 0.0.0.0/00.0.0.0/0 with the next hop type set to Virtual Network Gateway to force all outbound internet traffic through an on-premises security appliance.
  3. Configure two multi-site HTTPS listeners: one for partners.contoso.com and one for internal.contoso.com. For partners.contoso.com, create a basic routing rule to the VM backend pool, set the backend protocol to HTTPS, upload the self-signed certificate (.cer) as a Trusted Root Certificate, and link VNet-Hub to the private.contoso.com private DNS zone. For internal.contoso.com, create a path-based routing rule with a default target pointing to the App Service backend pool, set the backend protocol to HTTP, enable host header override in the HTTP settings, and define a path map for /images/* pointing to the storage account backend pool. Apply an NSG to Subnet-GW with an inbound rule allowing GatewayManager traffic on ports 6520065200-6553565535 at priority 100100.Cevap
  4. D
    Configure two multi-site HTTPS listeners: one for partners.contoso.com and one for internal.contoso.com. For partners.contoso.com, create a basic routing rule to the VM backend pool, set the backend protocol to HTTPS, upload the self-signed certificate (.cer) as a Trusted Root Certificate, and link VNet-Hub to the private.contoso.com private DNS zone. For internal.contoso.com, create a path-based routing rule with a default target pointing to the App Service backend pool, set the backend protocol to HTTP, enable host header override in the HTTP settings, and define a path map for /images/* pointing to the storage account backend pool. Apply an NSG to Subnet-GW with an inbound rule allowing GatewayManager traffic on ports 6520065200-6553565535 at priority 40964096, which is lower precedence than a custom inbound deny-all rule set at priority 10001000.

Cevap

The correct configuration requires configuring two multi-site HTTPS listeners, linking VNet-Hub to the private DNS zone, overriding the backend host name for the App Service pool, using HTTPS with a Trusted Root Certificate for the VM pool, and applying a high-precedence inbound NSG rule on Subnet-GW allowing GatewayManager traffic.
The correct configuration addresses all requirements: (1) multi-site listeners are used for hosting multiple domains on the same IP and port; (2) VNet-Hub is linked to the private DNS zone so the gateway can resolve the VM backend pool's FQDNs; (3) backend HTTP settings use HTTPS with a Trusted Root Certificate for the VM pool, and HTTP with host header override for the multi-tenant App Service; (4) a path-based routing rule is configured for the site requiring path mapping; (5) the NSG allows GatewayManager traffic on ports 6520065200-6553565535 with higher precedence (lower priority number) than any deny rule.

Adım Adım Çözüm

1
Configure listeners for multi-site hosting.
Two multi-site HTTPS listeners are created on port 443443, one with host name partners.contoso.com and the other with internal.contoso.com, allowing them to share the same public IP address.
Basic listeners cannot differentiate traffic based on host headers, so multi-site listeners are required to host multiple domains on the same IP and port.
2
Configure DNS resolution for the gateway.
VNet-Hub (where the Application Gateway is deployed) is linked to the private DNS zone private.contoso.com.
The Application Gateway must resolve the FQDNs of the backend VMs. Linking only the spoke VNet would prevent the gateway in the hub VNet from performing resolution.
3
Configure backend settings for both pools.
The VM backend settings use HTTPS with the uploaded self-signed root certificate, while the App Service backend settings use HTTP and enable the override host name setting.
End-to-end SSL requires HTTPS backend settings. Self-signed certificates require a Trusted Root Certificate to be uploaded for verification. App Service requires host name override because it is a multi-tenant service.
4
Configure routing rules.
A basic routing rule links partners.contoso.com to the VM pool. A path-based routing rule links internal.contoso.com to the App Service pool by default, with a path map routing /images/* to the storage account.
Path-based routing is required to separate traffic based on URL subpaths, while basic routing is sufficient for single-target domains.
5
Secure the subnet using NSG rules.
An NSG is applied to Subnet-GW with an inbound rule allowing ports 6520065200-6553565535 from the GatewayManager service tag, set at priority 100100.
Azure Application Gateway v2 requires communication with the Gateway Manager. The rule must have higher precedence (lower priority number) than any custom deny rules to avoid blocking management traffic.

Anahtar Kavram

Azure Application Gateway v2 configuration including multi-site listeners, path-based routing, backend certificate trust, DNS resolution dependencies, and subnet NSG requirements.
Tahmini Süre:3m 0s
Bu soruyu puanla