Azure Traffic Manager supports different routing methods. Which statement best describes how the Priority routing method works?
Think about how failover works when you want one main endpoint and backups.
The Priority routing method directs traffic to the highest priority endpoint that is healthy. If that endpoint is down, Traffic Manager fails over to the next priority endpoint.
Consider two endpoints configured in Azure Traffic Manager with weights 1 and 3 respectively using the Weighted routing method. Over time, what is the expected traffic distribution ratio?
Weights determine the proportion of traffic each endpoint receives.
The Weighted routing method distributes traffic proportionally to the weights assigned. Here, weight 1 gets 1/(1+3) = 25%, and weight 3 gets 75%.
You want to route users to the Azure Traffic Manager endpoint that responds the fastest from their location, minimizing latency. Which routing method achieves this?
Think about routing based on speed rather than location or priority.
The Performance routing method directs users to the endpoint with the lowest network latency, improving response times.
When using the Geographic routing method in Azure Traffic Manager, what is an important security consideration?
Consider how geographic location is determined and what can affect it.
Geographic routing relies on the user's IP address to determine location. Users can use VPNs or proxies to mask their IP, which may bypass geographic routing rules.
You have a multi-region Azure deployment and want to ensure users are routed to the primary region unless it is down, then failover automatically to a secondary region. Which Traffic Manager routing method best supports this scenario?
Think about failover and primary-secondary endpoint behavior.
Priority routing sends traffic to the highest priority endpoint and fails over to lower priority endpoints only if the primary is unhealthy, making it ideal for disaster recovery.