You operate multiple public endpoints for an e-commerce platform in different regions. You must ensure users are directed to endpoints based on the country or region they originate from to meet data sovereignty requirements. Which Azure Traffic Manager routing method should you use?

The Geographic routing method in Azure Traffic Manager directs users to specific endpoints based on the geographic location of their DNS query. This is ideal for meeting data sovereignty requirements, as it ensures users from a particular country or region are routed to an endpoint hosted within that same region. Performance routing directs users to the endpoint with the lowest latency, which doesn't guarantee data sovereignty. Weighted routing distributes traffic based on assigned weights, not geographic origin. Priority routing sends all traffic to a primary endpoint unless it's unavailable, also not addressing geographic requirements. MultiValue and Subnet are not standard Azure Traffic Manager routing methods.