What should you do?

You recently migrated a monolithic application to Google Cloud by breaking it down into microservices. One of the microservices is deployed using Cloud Functions. As you modernize the application, you make a change to the API of the service that is backward-incompatible. You need to support both existing callers who use the original API and new callers who use the new API.

What should you do?
A . Leave the original Cloud Function as-is and deploy a second Cloud Function with the new AP
B . Use a load balancer to distribute calls between the versions.
C . Leave the original Cloud Function as-is and deploy a second Cloud Function that includes only the changed AP
D . Calls are automatically routed to the correct function.
E . Leave the original Cloud Function as-is and deploy a second Cloud Function with the new AP
F . Use Cloud Endpoints to provide an API gateway that exposes a versioned AP
H . Re-deploy the Cloud Function after making code changes to support the new AP
. Requests for both versions of the API are fulfilled based on a version identifier included in the call.

Answer: D

Explanation:

Reference: https://cloud.google.com/endpoints/docs/openapi/versioning-an-api