Bird
Raised Fist0
Azurecloud~5 mins

Traffic Manager routing methods in Azure - Cheat Sheet & Quick Revision

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Recall & Review
beginner
What is the purpose of Azure Traffic Manager?
Azure Traffic Manager directs user traffic to the most appropriate service endpoint based on routing methods, improving availability and responsiveness.
Click to reveal answer
beginner
Explain the 'Priority' routing method in Traffic Manager.
Priority routing sends all traffic to the primary endpoint unless it is unhealthy, then it fails over to the next priority endpoint.
Click to reveal answer
intermediate
How does the 'Weighted' routing method work?
Weighted routing distributes traffic across endpoints based on assigned weights, allowing control over traffic proportions sent to each endpoint.
Click to reveal answer
intermediate
Describe the 'Performance' routing method.
Performance routing directs traffic to the endpoint with the lowest network latency from the user, improving response times.
Click to reveal answer
intermediate
What is the 'Geographic' routing method used for?
Geographic routing sends users to endpoints based on their geographic location, useful for compliance or localization needs.
Click to reveal answer
Which Traffic Manager routing method sends all traffic to a primary endpoint unless it is down?
AWeighted
BPriority
CPerformance
DGeographic
What does the Weighted routing method allow you to do?
ASend all traffic to one endpoint
BSend traffic based on user location
CSend traffic to the fastest endpoint
DDistribute traffic based on assigned weights
Which routing method improves user experience by reducing latency?
APriority
BWeighted
CPerformance
DGeographic
Geographic routing is best used when you want to:
ASend traffic based on user location
BBalance traffic evenly
CFailover automatically
DSend traffic to the fastest endpoint
If you want to test a new endpoint with a small portion of traffic, which routing method should you use?
AWeighted
BGeographic
CPerformance
DPriority
Describe the main differences between Priority and Weighted routing methods in Azure Traffic Manager.
Think about failover versus traffic sharing.
You got /4 concepts.
    Explain how Performance and Geographic routing methods improve user experience.
    Consider speed and location factors.
    You got /4 concepts.

      Practice

      (1/5)
      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