Question

Difficulty: EasyConfigure Azure Application Gateway

A company has a single web application hosted on Azure Virtual Machines. You are configuring an Azure Application Gateway to distribute traffic. You need to ensure that requests for the URL path `/videos/*` are directed to a pool of VMs optimized for video streaming, while all other requests are directed to a default pool of web servers. Which type of routing rule should you configure on the Application Gateway?

  1. A
    Basic routing rule
  2. B
    Session affinity routing rule
  3. Path-based routing ruleAnswer
  4. D
    Round-robin routing rule

Answer

Path-based routing rule
A path-based routing rule allows you to create a URL path map. This map defines rules that associate specific path patterns, like `/videos/*`, with designated backend pools. Any request that does not match the specified paths is routed to the default backend pool, which satisfies the requirements of the scenario.

Step-by-Step Solution

1
Analyze the traffic routing requirements.
Traffic must be directed to different backend pools based on the request URL path (specifically `/videos/*`).
Understanding the condition for routing is the first step to selecting the correct rule type.
2
Compare the available Application Gateway routing rule options in Azure.
Basic routing rules route all traffic to a single backend pool. Path-based routing rules use URL path maps to route requests to different backend pools based on the path.
This determines which rule type supports path-based conditions.
3
Select the rule type that matches the requirement.
A path-based routing rule is required to inspect the URL path and forward traffic to the video-optimized backend pool.
Only a path-based routing rule matches the requirement to inspect and route traffic based on URL paths.

Key Concept

Azure Application Gateway routing rules decide how to route traffic from the listener to backend pools. A basic rule routes all traffic unconditionally, whereas a path-based rule uses a URL path map to route traffic to specific backend pools based on the URL path in the request.
Estimated Time:45s
Rate this question