Google Cloud Professional Cloud Architect — Question 37

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?

Answer options

• A. Configure a new load balancer for the new version of the API
• B. Reconfigure old clients to use a new endpoint for the new API
• C. Have the old API forward traffic to the new API based on the path
• D. Use separate backend pools for each API path behind the load balancer

Correct answer: D

Explanation

The correct answer is D because using separate backend pools allows the load balancer to direct traffic appropriately for each API version while maintaining the same SSL and DNS settings. Option A introduces unnecessary complexity and doesn't address the need to support both APIs simultaneously. Option B would disrupt existing clients by requiring changes to their configurations, which is not ideal. Option C might lead to performance issues or additional latency due to the extra forwarding step.