Apigee is deployed in two regions with region-local backends; route requests to the corresponding local backend per region.

The correct approach is to create a TargetServer for each regional backend and use the system.region.name variable within the API proxy to dynamically select the appropriate TargetServer. This ensures requests are routed to the backend in the same region as the Apigee instance processing the request, achieving regional locality. Creating a TargetEndpoint with weighted load balancing (option 1) would distribute traffic across all backends, not necessarily keeping it regional. Using regional internal Application Load Balancers (option 2) adds unnecessary complexity and doesn't directly integrate with Apigee's dynamic routing capabilities for this specific use case. A global external Application Load Balancer (option 3) would centralize traffic, defeating the purpose of regional backends and potentially increasing latency.