Traffic Manager routing methods in Azure - Step-by-Step Execution

Process Flow - Traffic Manager routing methods

User DNS Request

↓

Traffic Manager receives request

↓

Evaluate routing method

↓

Priority?

↓

Weighted?

↓

Performance?

↓

Geographic?

↓

Multivalue?

↓

Subnet?

↓

Return selected endpoint IP to user

↓

User connects to endpoint

Traffic Manager receives a DNS request and selects an endpoint based on the configured routing method, then returns the endpoint IP to the user.

Execution Sample

Azure

User DNS request -> Traffic Manager -> Routing method evaluation -> Endpoint IP returned

This flow shows how Traffic Manager routes user requests based on different routing methods.

Process Table

Step	Routing Method	Condition Evaluated	Selected Endpoint	Reason
1	Priority	Is highest priority endpoint healthy?	Endpoint A	Endpoint A is highest priority and healthy
2	Priority	Is highest priority endpoint healthy?	Endpoint B	Endpoint A unhealthy, Endpoint B next priority healthy
3	Weighted	Random weighted selection	Endpoint C	Endpoint C selected based on weight 70%
4	Weighted	Random weighted selection	Endpoint D	Endpoint D selected based on weight 30%
5	Performance	Measure latency from user to endpoints	Endpoint B	Endpoint B has lowest latency
6	Geographic	User IP in Europe region?	Endpoint E	User located in Europe region
7	Multivalue	Return multiple healthy endpoints	Endpoints A, B	Both endpoints healthy, returned together
8	Subnet	User IP in subnet 10.0.0.0/24?	Endpoint F	User IP matches subnet assigned to Endpoint F
9	End	No more routing decisions	N/A	Routing complete, endpoint IP returned

💡 Routing method selects endpoint based on health and method rules; process ends after endpoint IP is returned.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7	After Step 8	Final
Selected Endpoint	None	Endpoint A	Endpoint B	Endpoint C	Endpoint D	Endpoint B	Endpoint E	Endpoints A, B	Endpoint F	Endpoint F

Key Moments - 3 Insights

Why does Traffic Manager choose Endpoint B in step 2 instead of Endpoint A?

Because Endpoint A is unhealthy at that time, so Traffic Manager selects the next highest priority healthy endpoint, Endpoint B, as shown in execution_table row 2.

How does the Weighted routing method decide which endpoint to select?

It uses random selection weighted by configured percentages. For example, Endpoint C has 70% weight and Endpoint D 30%, so Endpoint C is more likely selected, as shown in rows 3 and 4.

What happens if multiple endpoints are healthy in Multivalue routing?

Traffic Manager returns multiple healthy endpoints together to the user, allowing client-side load balancing, as shown in row 7.

Visual Quiz - 3 Questions

Look at the execution_table, which endpoint is selected at step 5 using Performance routing?

A Endpoint A

B Endpoint B

C Endpoint C

D Endpoint D

💡 Hint

Check execution_table row 5 under Selected Endpoint column.

At which step does Traffic Manager return multiple endpoints together?

A Step 7

B Step 6

C Step 3

D Step 8

💡 Hint

Look for Multivalue routing in execution_table and see which step returns multiple endpoints.

If Endpoint A becomes healthy again, which step would select it in Priority routing?

A Step 2

B Step 4

C Step 1

D Step 6

💡 Hint

Priority routing selects highest priority healthy endpoint as in step 1.

Concept Snapshot

Traffic Manager routes user DNS requests to endpoints based on routing methods:
- Priority: chooses highest priority healthy endpoint
- Weighted: selects endpoint randomly by weight
- Performance: chooses lowest latency endpoint
- Geographic: routes by user location
- Multivalue: returns multiple healthy endpoints
- Subnet: routes by user IP subnet
Each method evaluates health and rules before returning endpoint IP.

Full Transcript

Traffic Manager receives a DNS request from a user. It evaluates the configured routing method to decide which endpoint to send the user to. For Priority routing, it picks the highest priority endpoint that is healthy. If that endpoint is unhealthy, it picks the next priority. Weighted routing randomly selects an endpoint based on assigned weights. Performance routing chooses the endpoint with the lowest latency from the user. Geographic routing selects an endpoint based on the user's location. Multivalue routing returns multiple healthy endpoints to the user. Subnet routing selects an endpoint based on the user's IP subnet. After selecting the endpoint, Traffic Manager returns its IP address to the user, who then connects to that endpoint. This process ensures users are routed efficiently and reliably based on the chosen method.

Practice

1. Which Azure Traffic Manager routing method directs user traffic to the endpoint with the lowest network latency?

easy

A. Performance routing

B. Priority routing

C. Weighted routing

D. Geographic routing

Solution

1. Step 1: Understand routing methods

   Performance routing sends users to the endpoint with the lowest latency to improve speed.

2. Step 2: Compare other methods

   Priority routing sends traffic to a primary endpoint first; weighted routing distributes traffic by weights; geographic routing directs based on user location.

3. Final Answer:

   Performance routing -> Option A

4. Quick Check:

   Lowest latency = Performance routing [OK]

Hint: Lowest latency means Performance routing [OK]

Common Mistakes:

• Confusing Priority routing with Performance routing
• Thinking Weighted routing balances by speed
• Assuming Geographic routing uses latency

2. Which routing method syntax correctly assigns 70% traffic to endpoint A and 30% to endpoint B in Azure Traffic Manager?

easy

A. weighted: endpointA=70, endpointB=30

B. priority: endpointA=70, endpointB=30

C. performance: endpointA=70, endpointB=30

D. geographic: endpointA=70, endpointB=30

Solution

1. Step 1: Identify routing method for traffic distribution

   Weighted routing uses weights (percentages) to distribute traffic among endpoints.

2. Step 2: Match syntax with method

   Only weighted routing uses weight values like 70 and 30; others do not use weights.

3. Final Answer:

   weighted: endpointA=70, endpointB=30 -> Option A

4. Quick Check:

   Weights = Weighted routing syntax [OK]

Hint: Weights mean Weighted routing method [OK]

Common Mistakes:

• Using Priority routing with weights
• Assuming Performance routing uses weights
• Confusing Geographic routing with weights

3. Given a Traffic Manager profile with Priority routing where endpoint1 has priority 1 and endpoint2 has priority 2, what happens if endpoint1 becomes unhealthy?

medium

A. Traffic is split evenly between endpoint1 and endpoint2

B. Traffic stops until endpoint1 recovers

C. Traffic is routed to endpoint2

D. Traffic is routed based on geographic location

Solution

1. Step 1: Understand Priority routing behavior

   Priority routing sends all traffic to the highest priority healthy endpoint.

2. Step 2: Analyze endpoint health impact

   If endpoint1 (priority 1) is unhealthy, Traffic Manager routes traffic to the next priority endpoint, endpoint2.

3. Final Answer:

   Traffic is routed to endpoint2 -> Option C

4. Quick Check:

   Unhealthy primary = failover to next priority [OK]

Hint: Failover sends traffic to next priority endpoint [OK]

Common Mistakes:

• Thinking traffic stops when primary is down
• Assuming traffic splits evenly in Priority routing
• Confusing geographic routing with priority failover

4. You configured Geographic routing but users from Europe are still routed to the US endpoint. What is the most likely cause?

medium

A. Endpoint monitoring is disabled

B. DNS TTL is set too low

C. Weighted routing is overriding Geographic routing

D. Geographic regions are overlapping or misconfigured

Solution

1. Step 1: Understand Geographic routing setup

   Geographic routing directs users based on their location mapped to specific endpoints.

2. Step 2: Identify misconfiguration impact

   If regions overlap or are misconfigured, users may be routed incorrectly, like Europe users going to US endpoint.

3. Final Answer:

   Geographic regions are overlapping or misconfigured -> Option D

4. Quick Check:

   Misconfigured regions cause wrong routing [OK]

Hint: Check region mappings for overlaps or errors [OK]

Common Mistakes:

• Assuming monitoring affects geographic routing directly
• Confusing weighted routing with geographic routing
• Thinking DNS TTL causes wrong region routing

5. You want to ensure users in Asia always use a specific endpoint, but if it fails, traffic should go to the fastest available endpoint anywhere. Which routing method combination should you use?

hard

A. Weighted routing with Geographic fallback to Priority routing

B. Geographic routing with Priority fallback to Performance routing

C. Priority routing with Weighted fallback to Geographic routing

D. Performance routing with Priority fallback to Weighted routing

Solution

1. Step 1: Identify requirement for fixed region routing

   Geographic routing ensures users in Asia use the specific endpoint assigned to that region.

2. Step 2: Identify fallback for endpoint failure

   If the Asia endpoint fails, fallback should route to the fastest available endpoint globally, which is Performance routing.

3. Step 3: Combine routing methods

   Use Geographic routing as primary, with Priority routing configured to fallback to Performance routing for failover.

4. Final Answer:

   Geographic routing with Priority fallback to Performance routing -> Option B

5. Quick Check:

   Fixed region + failover to fastest endpoint = Geographic + Priority + Performance [OK]

Hint: Use Geographic for region, Performance for speed fallback [OK]

Common Mistakes:

• Mixing Weighted routing for fixed region needs
• Using Priority routing alone without geographic control
• Confusing fallback order and methods