Examkin

Question

Difficulty: MediumConfigure Azure Application Gateway

You are deploying a single Azure Application Gateway v2 to host two web applications: billing.contoso.com and claims.contoso.com. Both applications must share a single public IP address on the gateway, but traffic must be routed to separate backend pools: BillingPool and ClaimsPool. You need to configure the Application Gateway listeners and routing rules to ensure traffic is correctly directed to the appropriate backend pool. Which configuration should you implement?

  1. Create two multi-site listeners, one for billing.contoso.com and another for claims.contoso.com, and configure two basic routing rules to associate each listener with its respective backend pool.Answer
  2. B
    Create a single basic listener configured for the public IP address, and configure a path-based routing rule that routes traffic based on HTTP Host headers.
  3. C
    Create a single multi-site listener with the host name set to *.contoso.com, and configure a single basic routing rule with a redirection configuration to the backend pools.
  4. D
    Create two multi-site listeners, one for billing.contoso.com and another for claims.contoso.com, and configure a single path-based routing rule that references both listeners.

Answer

Create two multi-site listeners, one for billing.contoso.com and another for claims.contoso.com, and configure two basic routing rules to associate each listener with its respective backend pool.
Configuring separate multi-site listeners allows the Application Gateway to route traffic based on the Host header of incoming requests. Since each listener must be linked to its own backend pool, two separate routing rules are required to complete the configuration.

Step-by-Step Solution

1
Create two backend pools: BillingPool and ClaimsPool.
The backend pools are provisioned and ready to receive traffic.
The gateway needs targets to route traffic to for each application.
2
Configure two multi-site listeners, one with host name billing.contoso.com and the other with claims.contoso.com.
The Application Gateway is configured to listen for requests arriving on the single public IP address with specific Host headers.
Multi-site listeners evaluate the HTTP Host header of incoming requests to distinguish between different domains.
3
Create two basic routing rules to link each listener to its corresponding backend pool.
Requests for billing.contoso.com are forwarded to BillingPool, and requests for claims.contoso.com are forwarded to ClaimsPool.
Each listener must have its own routing rule to map requests to the correct backend pool.

Key Concept

Multi-site hosting and routing configuration on Azure Application Gateway
Estimated Time:1m 30s
Rate this question

Topics

Configure Azure Application Gateway

More questions from this topic