Your company has decided to make a major revision of their API in order to create better experiences for their developers. They need to keep the old version of the API available and deployable, while allowing new customers and testers to try out the new API. They want to keep the same SSL and DNS records in place to serve both APIs. What should they do?

Using separate backend pools for each API path behind a load balancer allows you to serve both the old and new API versions under the same SSL certificate and DNS record. The load balancer can route requests to the appropriate backend pool based on the URL path, effectively managing both versions simultaneously. Configuring a new load balancer for the new API would require new DNS records or complex DNS routing, which goes against the requirement to keep the same DNS records. Reconfiguring old clients to use a new endpoint is not feasible if the goal is to keep the old API available and accessible via the existing endpoint. Having the old API forward traffic to the new API based on the path would introduce unnecessary latency and complexity, and it doesn't allow for independent deployment and management of the new API.