Practice Test 3 | Google Cloud Certified Professional Cloud Architect | Dumps | Mock Test
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?
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
Feedback
A – Configure a new load balancer for the new version of the API.
Then you’ll have two load balancers: new and old one. This would break the API contract and also need to configure SSL and DNS for new load balancer
B – Reconfigure old clients to use a new endpoint for the new API.
This would break the contract between client and API and also can no longer reach to old API.
C – Have the old API forward traffic to the new API based on the path.
This is against the design principle and best practice for webservices API. API should not play this role – API should not know how to route client requests. In fact, API even shouldn’t have knowledge about client at all.
D (Correct answer) – Use separate backend pools for each API path behind the load balancer.
This solution meets both requirements: continue servicing old and new API and keep the same SSL and DNS records
Further Explanation
HTTP(S) Load Balancing configuration and it backend service: A configured backend service contains one or more backends.
Here is demonstrating configuration for the concept similar to the question scenarios: you just need to configure URL mapping pointing to the new and old APIs which are hosted in corresponding backends – this implementation meets all the requirement: No contract breaking; clients continue to access new and old API without reconfigure SSL and DNS
References
Setting Up HTTP(S) Load Balancing https://cloud.google.com/compute/docs/load-balancing/http/
Backend service components: https://cloud.google.com/compute/docs/load-balancing/http/backend-service
Creating Content-Based Load Balancing https://cloud.google.com/load-balancing/docs/https/content-based-example
Comments are closed, but trackbacks and pingbacks are open.