Traffic Manager routing methods in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the routing method to prioritize the endpoint with the lowest latency.

Azure

az network traffic-manager profile create --name MyProfile --resource-group MyResourceGroup --routing-method [1]

Drag options to blanks, or click blank then click option'

APerformance

BWeighted

CPriority

DGeographic

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing Priority instead of Performance routing.

Using Geographic routing which routes by location, not latency.

The Performance routing method directs traffic to the endpoint with the lowest latency.

2fill in blank

medium

Complete the code to create a Traffic Manager profile that distributes traffic based on assigned weights.

Azure

az network traffic-manager profile create --name MyProfile --resource-group MyResourceGroup --routing-method [1]

Drag options to blanks, or click blank then click option'

APriority

BWeighted

CMultivalue

DPerformance

Attempts:

3 left

💡 Hint

Common Mistakes

Using Priority routing which sends all traffic to the highest priority endpoint.

Confusing Performance routing with Weighted routing.

The Weighted routing method distributes traffic based on weights assigned to each endpoint.

3fill in blank

hard

Fix the error in the code to use the routing method that sends traffic to the endpoint with the highest priority.

Azure

az network traffic-manager profile create --name MyProfile --resource-group MyResourceGroup --routing-method [1]

Drag options to blanks, or click blank then click option'

AWeighted

BSubnet

CPriority

DPerformance

Attempts:

3 left

💡 Hint

Common Mistakes

Using Weighted routing which splits traffic instead of prioritizing.

Choosing Performance routing which routes by latency.

The Priority routing method sends all traffic to the endpoint with the highest priority (lowest number).

4fill in blank

hard

Fill both blanks to create a Traffic Manager profile using Geographic routing and specify the resource group.

Azure

az network traffic-manager profile create --name MyProfile --resource-group [1] --routing-method [2]

Drag options to blanks, or click blank then click option'

AMyResourceGroup

BWeighted

CGeographic

DPriority

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up routing methods or resource group names.

Using Priority or Weighted routing instead of Geographic.

Use MyResourceGroup for the resource group and Geographic routing to route traffic based on user location.

5fill in blank

hard

Fill all three blanks to create a Traffic Manager profile with Multivalue routing, specify the resource group, and name the profile.

Azure

az network traffic-manager profile create --name [1] --resource-group [2] --routing-method [3]

Drag options to blanks, or click blank then click option'

AMyProfile

BMyResourceGroup

CMultivalue

DPerformance

Attempts:

3 left

💡 Hint

Common Mistakes

Using Performance routing instead of Multivalue.

Swapping resource group and profile name.

Set the profile name to MyProfile, resource group to MyResourceGroup, and routing method to Multivalue which returns multiple healthy endpoints.

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