An international SaaS provider is evaluating Traffic Manager routing methods. They need a concise mapping of behaviors: which method picks the lowest network latency from the user, which distributes according to configured endpoint weights, which routes users based on their geographic location, and which returns multiple healthy endpoints in DNS responses for client-side selection?

The correct answer accurately describes the function of each Azure Traffic Manager routing method. Performance routing directs users to the endpoint with the lowest network latency, which is typically the closest healthy endpoint. Weighted routing distributes traffic among endpoints based on predefined weights, allowing for proportional traffic allocation. Geographic routing routes users to specific endpoints based on the geographic location of their DNS query source IP address. Multivalue routing returns multiple healthy endpoints in a single DNS response, enabling client-side retry logic and improved availability. The incorrect options misattribute the core functionality of these distinct routing methods.